Differences

This shows you the differences between two versions of the page.

--- public:i-700-abms-08-1:final_project:cdm-s_extended [2008/04/21 17:35] – marco
+++ public:i-700-abms-08-1:final_project:cdm-s_extended [2024/04/29 13:33] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 [[internal:cdm-s:main|CDM-S]]
@@ Line 19: / Line 20: @@
   * //How is it processed/changed//: The data is processed inside all the modules. All of them have tasks to do meanwhile they are exchanging messages with the other modules. The system will evolve itself just using its modules and their simple functions.
-This accomplish **steps 1 and 2** of the CDM-s in which we should define objectives and questions to answer to during and at the end of the simulation.\\
+This accomplishes **steps 1 and 2** of the CDM-s in which we should define objectives and questions to answer to during and at the end of the simulation.\\
 In **step 3** we had to define:
@@ Line 29: / Line 30: @@
 This was one of the hardest step to go through because all the debugging, troubleshooting and important decision were made in this step after experiencing all the possible behaviors of the system.\\
 We got stuck on this step because most of the important decision/problems are supposed to come up here.\\
-  * //Expected communications//: obviously we were really far from the expected system. Our modules were drowning the WhiteBoard because they were too fast to post messages and then some of the modules or even the Market were crashing. The solution was just slowing down the speed of the modules with a timer that allows all the publication/subscription to be successfully.
+  * //Expected communications//: obviously we were really far from the expected system. Our modules were drowning the WhiteBoard because they were too fast to post messages and then some of the modules or even the Market were crashing. The solution was just slowing down the speed of the modules with a timer that allows all the publication/subscription to be successfull.
   * //Efficient information flow//: this part was really helpful once improved. We needed to have a lot of information to be exchanged among the modules and we started giving static hardcoded parameters, then we moved to the command line options and then again we throwed all the "variable" values to the psySpec file as it is really easy to configure.
   * //Convenience with regard to programming languages and executables//: we decided according to the teacher to use java because of its portability (and also because of the skills of most of the students). It could have been really an effort to use a c/c++ environment since we are three different users (mac, linux, windows), and again because we could have used a lot of code from the last year simulation. So the choice of using java was the most obvious.
@@ Line 37: / Line 38: @@
 **Step 6**: assigning modules to team members.\\
-..this was easy :) Marco was assigned to the Market, Ivar started to code the Industry module, and Vigdis was feeding the others with equations and numbers. The "math" work wasn't a real module assignement but it was clearly a very big effort since the numbers and the equations are gathered manually from all over the Internet under supervision of Rognvaldur.
+..this was easy :) Marco was assigned to the Market, Ivar started to code the Industry module, and Vigdis was feeding the others with equations and numbers. The "math" work wasn't a real module assignement but it was clearly a very big effort since the numbers were gathered manually from all over the Internet under supervision of Rognvaldur.
 **Step 7**: starting to code.\\
@@ Line 47: / Line 48: @@
 After that we finally had our first version (**0.2** in the svn repository) and we tested the system as described in **step 8**:\\
-The system was working and doing what it was expected to do without errors, but after 10 seconds it stopped. The reason is that the modules had short life. The way we gave them parameters and demand functions was bad implemented (see step 9).
+The system was working and doing what it was expected to do without errors, but after 10 seconds it stopped. The reason is that the modules had short life. The way we gave them parameters and demand functions was badly implemented (see step 9).
 **Step 9: Build Modules to specification.**\\
-This step was the most brain consuming! This was the main aim of the topic and we are not economist and neither mathematics so we spent lot of hours deciding what equations and values to implement in the psySpec and inside the Industry module.\\
+This step was the most brain consuming! This was the main aim of the topic and we are not economist so we spent lot of hours deciding what equations and values to implement in the psySpec and inside the Industry module.\\
 In this step we started to really need the timing.. it's been impossible to go on coding without a clock. So back to **step 7** and building a Timer class. After that, again to **step 4** to test the whole system with the new module.