-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spotpy's SCE-UA application frozen after some trys #283
Comments
hi @lingchengli , have you solve it? I have same issue, do you have any suggestion? |
I have figured my problem out, I use "nohup" for mpirun, the process would be killed after terminal closed. Alternative way is using "screen". |
Not yet, i still have the same issue. For my case, I submitted the job, so it should not be related to the terminal closed ? |
@junyinglucn could you show your solution code here, thanks? |
Hi, @thouska, do you have some great suggestions, many thanks :D |
Hi,@lingchengil did u solve the problem? |
@lingchengli did u solve the problem related to freezing? |
Hi @thouska,
Thanks for developing Spotpy. I am applying spotpy to calibrate one model, using sceua method. The simple setting code is shown below. I prepared the spot_setup file to link spotpy with the model.
The code runs successfully at the beginning. I submit the mpi job using "mpirun -n 200 python xxx.py". It generates different parameter sets, does the simulations, calculates the objective functions, and continues to write results (e.g., like, simulations) to the fout file.
However, after several hundreds of trys, let's say 400 records. There are 400 lines in the fout files, recording the calibration results from the code. The 400 records are less than my rep setting of 1000. It won't generate any more trys and won't add more lines in the fout file. The code is just frozen at this point until reaching the submitted job's time limit.
I don't know why this happens. If the model setting (e.g., data, or parameters) is not right, it should not work at the very beginning.
It only happens after some runs.
Do you have some suggestions and comments?
Many thanks,
The text was updated successfully, but these errors were encountered: