0) To make sure the optimizer functions properly before even running the optimization, one can run the following code and make sure that there is no error code.

python -f test.*.eval.txt -v 2, where * can be changed to whatever type of injector one is running.

If you have trouble running the optimizer, go through these steps to try to locate the problem.

1) Check that nohup.out is empty.

2) Look at optexch/RUN01_his to see if the objectives and the constraints are 8e88. Seeing this value means that each evaluation is returning an error. If this occurs, stop the optimizer (using the command "touch bailout" and by stopping spea2). Then take the RUN01_his file and make that the input used in optconf/var_param. When changing var_param, change, change the line "clean up files" to "No".

3) Look in the /tmp directory and look at each job's message (_0000Job#.msg). Check to see if there is an error written.  The line "id: cannot find name for group ID 20073" does not indicate any problems.


Some other linux code that is useful when it comes to debugging:

See what programs are running: lsof +D .

Injector Optimization Home

Topic attachments
I Attachment Action Size Date Who CommentSorted ascending
Debugging.JPGJPG Debugging.JPG manage 56 K 23 Feb 2019 - 20:26 UnknownUser  
This topic: PhotocathodeBrightBeams/Private > WebHome > InjectorOptimization > Debugging
Topic revision: 07 May 2019, el535
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding CLASSE Wiki? Send feedback