lizhen-dlut / solfec

Automatically exported from code.google.com/p/solfec
0 stars 0 forks source link

duration parameter in RUN() ignored #17

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Run balls.py example

What is the expected output? What do you see instead?
Analysis should end at 0.497 seconds as defines RUN (solfec, gs, 0.497)
However keeps going until stopped by the user.

What version of the product are you using? On what operating system?
0.596 windows xp 32bit exe

Please provide any additional information below.

Original issue reported on code.google.com by steve.br...@atkinsglobal.com on 1 Jun 2011 at 11:39

GoogleCodeExporter commented 8 years ago
Please specify the command line options:

./solfec -w inp/balls.py

will run the analysis as required (without the viewer)

./solfec -w -v inp/balls.py

will run the analysis as long as the user (in the viewer mode) requests. In the 
viewer mode, the duration from RUN (...) is overwritten.

Original comment by t.kozi...@gmail.com on 1 Jun 2011 at 12:30

GoogleCodeExporter commented 8 years ago
Thanks. Had just come back to add it's only in Viewer mode. I'm not sure that's 
generally sensible behaviour though - often inputs etc may not be valid past 
the end of the time specified for analysis.  I guess the answer is that 
actually running analyses in Viewer mode isn't a very sensible thing to do 
anyway.

Original comment by steve.br...@atkinsglobal.com on 1 Jun 2011 at 1:07

GoogleCodeExporter commented 8 years ago
I can easily change it so that duration in the RUN command complies with the 
one possible in the viewer. I am not sure whether this is fully justified:

there can be a number of RUN() commands in the input file for several stages of 
the analysis. In the viewer mode these are ignored. As you said: the viewer 
analysis mode is only auxiliary.

Original comment by t.kozi...@gmail.com on 1 Jun 2011 at 1:17

GoogleCodeExporter commented 8 years ago
Agree.  Suggest a note is just added to the RUN() command in the documentation.

Original comment by steve.br...@atkinsglobal.com on 1 Jun 2011 at 2:00

GoogleCodeExporter commented 8 years ago
OK. A comment has been added in the manual.

Original comment by t.kozi...@gmail.com on 5 Jul 2011 at 2:18