Re: [scipion-users] scipion 3.0.3+ does not support multiple queue configurations anymore?

[Pablo C. <pc...@cn...>]

hi

On 5/10/20 16:22, Lugmayr, Wolfgang wrote:
> hi,
>
> now it works, but only if you have a "default" entry in the queue 
> section of the hosts.conf. i have renamed this one and then the 
> "Execute" selection does not work.
> maybe add a comment in the hosts.conf template.
Thanks Wolfgang, we then need to review this behavior. Certainly, 
"default" shouldn't be "that important".
>
> i found also the "Edit" button beside the "Use queue" entry. so we can 
> re-submit/continue also existing jobs to gpus or cpus depending what's 
> available.
>
> good work ;-)
>
Thank you, it was a last addition based on other user/developer 
feedback. Scipion3 is far more agile to incorporate new features quickly.
> cheers,
> wolfgang


All the best, Pablo

>
>
> ------------------------------------------------------------------------
> *From: *"Pablo Conesa" <pc...@cn...>
> *To: *"Mailing list for Scipion users" 
> <sci...@li...>
> *Sent: *Monday, 5 October, 2020 12:15:24
> *Subject: *Re: [scipion-users] scipion 3.0.3+ does not support 
> multiple queue configurations anymore?
>
> Hi Wolfgang ... we have recently added a new feature that is releated 
> to the queue parameters.
>
> With the latest version you can edit the parameters before 
> "executing/scheduling" the protocol.
>
> If they are populated (copying a protocol will keep the parameters) 
> the user is not asked.
>
> We were currenlty discussing this, and Jose Miguel already suggested 
> to ask, at least once to verify de queue parameters and we will do so.
>
> Maybe, with current code (3.0.4), you can remove the queue parameters 
> in the template, so users will be asked. (I'm guessing you have 
> queueParams poplated in your template)
>
> Does it make sense?
>
>
>
>
>
> On 5/10/20 11:29, Lugmayr, Wolfgang wrote:
>
>     hi,
>
>     we have 2 queues on our cluster, one for cpu jobs and one for gpu jobs.
>     so far my template was working fine, but since 3.0.3 and now 3.0.4 scipion always takes the last entry in the QUEUES section of the hosts.conf file.
>
>     before a window pop-up appeared after pressing the Execute button and users could choose which queue and which parameters they want to have.
>     this defines the nodes the users will get.
>
>     now the pop-up window is gone and the job script is generated with the settings of the last queue entry.
>     in this case maxwell-gpu.
>
>     QUEUES = {
>          "maxwell-cpu": [
>              ["JOB_QUEUE","cssb,all","Queue Name:","Select the target queue/partition"],
>              ["JOB_TIME", "168", "Time (hours)", "Select the time expected (in hours) for this job"],
>              ["JOB_NODES","48","Total cores:","MPI tasks"],
>              ["JOB_CONS","Gold-6126","Constraints:","Call sinfo_detailed on the commandline for the options"]
>          ],
>          "maxwell-gpu": [
>              ["JOB_QUEUE","cssbgpu,allgpu","Queue Name:","Select the target queue/partition"],
>              ["JOB_TIME", "168", "Time (hours)", "Select the time expected (in hours) for this job"],
>              ["JOB_NODES","1","Total cores:","1: Single program call with threads and no MPI"],
>              ["JOB_CONS","GPUx1","Constraints:","Call sinfo_detailed on the commandline for the options"]
>          ]
>          }
>
>     is there a new way to do this, so i have to update my template?
>
>     cheers,
>     wolfgang
>
> -- 
> Pablo Conesa - *Madrid Scipion <http://scipion.i2pc.es> team*
>
>
> _______________________________________________
> scipion-users mailing list
> sci...@li...
> https://lists.sourceforge.net/lists/listinfo/scipion-users
>
>
> _______________________________________________
> scipion-users mailing list
> sci...@li...
> https://lists.sourceforge.net/lists/listinfo/scipion-users
-- 
Pablo Conesa - *Madrid Scipion <http://scipion.i2pc.es> team*