When a cell value filename is used in a model definition (initialCellsValue clause), it is automatically lowercased before attepting to read it. This may lead to errors if the filename has at least an uppercase letter (see e.g. issue #2).

Until this is fixed, the suggested workaround is to use lowercase cell value filenames.

The goal is to improve the pulse example by e.g. printing internal simulator times for each model transition.

When using the isUndefined function as defined in the cd++ manual

Signature: isUndefined : Real → Bool
Description: Returns True if the value is undefined, else returns False.

I get a parsing error for several cases. The only working one is for a concrete value (isUndefined(4))

I attached the ma file with the different cases (undefBugTest.ma). Each one can be tested individually by commenting the others.

The cases are:

  isUndefined(4)	 and 			% ok
  not isUndefined(4) 	 and			% ok
  isUndefined( $var1 )   and			% not ok: Parsing error syntax error, unexpected ')', expecting '!'
  isUndefined( $var2 )   and			% not ok: Parsing error syntax error, unexpected ')', expecting '!'
  isUndefined( $var2 ! 0) and			% ok: But dont know why. I Asume that takes $var2 as a tuple
  isUndefined( $var2 ! 4) and			% ok: But dont know why. I Asume that takes $var2 as a tuple
  isUndefined(?)	  and			% not ok: Parsing error syntax error, unexpected UNDEF
  isUndefined( [?]!0 )    and			% ok: I asume that what happens is that isUndefined expects a tuple. But don't work with plain undef value
  isUndefined( (0,0)~port1 )			% not ok: Parsing error syntax error, unexpected ')', expecting '!'

For the execution:
TIME=00:00:10:000
SIMU_ARGS="$SIMU_ARGS -t$TIME"

undefBugTest.ma.txt

As DEVNOTRANDOM is defined in Makefile.defs, randoms generators don't work properly.

This is to improve command line argument parsing so that e.g. arguments can be separated by spaces from their options.

This is to modify the presentation banner in order to display current, up-to-date information (i.e. simulator name, version, date and authors).

Hi again, I compiled my test and got an error. The solution was to change Uppercase to Lowercase of the TestEvacuacion03.val -> testevacuacion03.val

Error

With Solution

my file TestEvacuacion03.ma

Best Regards
Exequiel

This is to add a basic guideline to post-process and analyze pulse simulation outputs via Python notebooks.

UPDATED!edit 2:12am
*.log01 works well so far, but my directory is full withs others LOGs

Good morning, I have problems with LOGS, multiple LOGS appear when the simulation ends

run simulation

multiples LOGS

Which option do I have to choose?

I Have this LOG, always *.log01 more kb than rest LOGS

Is *.log01 able for use in the projects?

best regards
Exequiel

Under certain circumstances, the usage of state variables in simple Cell-DEVS models may lead to crashes. This model can be used to reproduce this unexpected behavior.

Hi, I compiled this version but i have issues with command "cd++"

When running the following coupled model:

[top]
components : persona gen@generator
% link : out@gen in@persona

[gen]
distribution : exponential
mean : 3
initial : 1
increment : 0 
out : out

[persona]
type : cell
border : nowrapped
delay : transport
defaultDelayTime : 100
dim : (20, 20)
initialvalue : 0
in : in
link : in in@persona(1,0)
neighbors :                              persona(-2,0) 
neighbors :               persona(-1,-1) persona(-1,0) persona(-1,1) persona(-1,2)
neighbors : persona(0,-2) persona(0,-1) persona(0,0) persona(0,1) persona(0,2)
neighbors :               persona(1,-1) persona(1,0) persona(1,1) persona(1,2)
neighbors :                              persona(2,0) 
localtransition: persona-rule
initialrowvalue : 3 10101

[persona-rule]
rule : 0 400 {(0,0)=1 and (0,1) = 0 and(0,2) != 2}
rule : 1 400 {(0,0)=0 and (0,1) != 2 and (0,-1) = 1}
rule : 0 400 {(0,0)=1 and (0,1)!=0 and(1,0)=0 and (1,1)!=2 and (1,-1)!=1}
rule : 1 400 {(0,0)=0 and (-1,0)=1 and (-1,1)!=0 and (0,1)!=2 and (0,-1)!=1}
rule : 0 400 {(0,0)=1 and ((0,1)=2 or(0,1)=3) and (1,0)!=0 and (-1,0)=0 and (-1,1)!=2 and (-1,-1)!=1}
rule : 1 400 {(0,0)=0 and (1,0)=1 and((1,1)=2 or (1,1)=3) and (2,0)!=0 and(0,1)!=2 and (0,-1)!=1}
rule : 0 400 {(0,0)=1 and (0,1)=0 and(0,2)=2 and (1,0)=0 and (1,1)!=2 and (1,-1)!=1}
rule : 1 400 {(0,0)=0 and (-1,0)=1 and (-1,2)=2 and (-1,1)=0 and (0,1)!=2 and (0,-1)!=1}
rule : 0 400 {(0,0)=1 and (0,1)=0 and(0,2)=2 and (1,0)!=0 and (-1,0)=0 and (-1,1)!=2 and (-1,-1)!=1}
rule : 1 400 {(0,0)=0 and (1,0)=1 and(1,2)=2 and (1,1)=0 and (2,0)!=0and (0,-1)!=1 and (0,1)!=2}
rule : {(0,0)} 100 {t} 

Then I would expect to generate ~400 log files (at least, one for each cell). Yet, it seems that it's stopping at ~100.
Note that changing the dimensions to dim : (5, 5) works fine.