Opened 4 months ago

Last modified 4 months ago

#2198 new defect

simfactory's user level run command does not record jobid in a segment's properties.ini file

Reported by: Roland Haas Owned by:
Priority: minor Milestone:
Component: SimFactory Version: development version
Keywords: Cc: qwang@…


The (user level) run command does not record a jobid in a segment's properties.ini file which means one cannot eg restart from a checkpoint since simfactory complains about an unset jobid:

simfactory/bin/sim create-run test1 --parfile par/tov_ETK_2018_lisbon.par --procs 1 --walltime 0:5:0
grep jobid ~/simulations/test1/output-0000/SIMFACTORY/properties.ini
shows the issue (but not producing any output). And the error obtained when trying to restart is along the lines of

Simulation name: binarybh9
Error: job id is negative
Aborting Simfactory

This was reported by Qingwen Wang in

A workaround is to not use run as a user but always submit or to use the cleanup command after which simfactory is fine with there not being a job id.

Attachments (0)

Change History (2)

comment:1 Changed 4 months ago by Ian Hinder

"sim run" doesn't create a job, because it doesn't use a queueing system. It seems to me that the bug here is that resuming from a checkpoint requires a job id.

comment:2 Changed 4 months ago by Roland Haas

The issue arises b/c simfactory wants to know "is the previous job still running?" when creating a new segment to know whether it can clean up the old one and / or has to chain a new segment or not.

Making "sim run" make up its own job id is just a hack to avoid this.

Modify Ticket

Change Properties
Set your email in Preferences
as new The ticket will remain with no owner.
Next status will be 'review'.
as The resolution will be set.
to The owner will be changed from (none) to the specified user.
Next status will be 'confirmed'.
The owner will be changed from (none) to anonymous.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.