Pardon the newbie question but I don’t see in the MATLAB App instructions where to put options for Slurm’s -A/–account. Is that what “Project” is for?
#### Failed to submit session with the following error:
sbatch: error: invalid partition specified: 1 sbatch: error: Batch job submission failed: Invalid partition name specified
Also when would this be useful, I’m guessing there are invalid characters for partition/account names?
* If this job failed to submit because of an invalid job name please ask your administrator to configure OnDemand to set the environment variable OOD_JOB_NAME_ILLEGAL_CHARS.
I would check your /var/log/ondemand-nginx/$USER/error.log for execve commands to see the exact sbatch command you’re issuing.
Yes, bc_account is for the account that you submit with, but the error seems to indicate the issue is with the partition you’re trying to use. Looking at the sbatch command will give us some insight into which partition you’re trying to use.
\"-A\", \"\", – the account you submit with appears to be an empty string. It seems like you should fill this out when you submit the app or remove it if you don’t need to specify the account.
I see - yes you’re using our accounts - or what we’d expect our accounts to look like. you see here the groups array is all of the groups you belong to that match the regular expression /^P./ (which is what OSC accounts look like).
<%-\
groups = OodSupport::User.new.groups.sort_by(&:id).tap \{ |groups|\
groups.unshift(groups.delete(OodSupport::Process.group))\
\}.map(&:name).grep(/^P./)\
-%>\
account:\
label: "Project"\
widget: select\
options:\
<%- groups.each do |group| %>\
- "<%= group %>"\
<%- end %>\
You have a couple options - remove all of this and use bc_account for a text field OR you can use auto_accounts if you’re on Slurm OR you can modify the grep expression to search for other groups you may be a part of.
Note that if you change account in the form - you’ll need to remove it from the submit.yml.erb file. bc_account and auto_accounts know how to submit themselves, so there’s no need for them in submit.yml.erb and you’ll keep getting empty strings if you keep account set there.
It’s here. Just replace account with auto_accounts in the form.yml.erb and get rid of all the references to account (specifically in the form and submit files).
It also mentions to enable Dynamic Form Widgets, but I don’t see a form.js file, since we upgraded from 1.7 up to 3.0, does it need to be manually created?
Yes delete all instances of account if you’re replacing it with auto_accounts.
The docs say
Prior to version 2.0, sites would have to make their own custom form.js to add dynamic behavior for batch connect forms. While sites can still have their own custom javascript, 2.0 added out of the box support for common use cases based on configuration.
so no you don’t need your own form.js if if you can configure the dynamic behavior you want in YAML. It seems like you’re just starting - so don’t add it until you find that you need to do something that we don’t support out of the box.
Also - thinking about this a little more - if you’re upgrading from 1.7, then your 1.7 application for Matlab should still work. All of these additions we’re talking about here are just that - additions. Additional things you could use like auto_accounts instead of supplying a list of valid accounts by hand. But even the hand built list in your 1.7 app will still work.
Failed to submit session with the following error:
sbatch: error: invalid partition specified: 1
sbatch: error: Batch job submission failed: Invalid partition name specified
This looks like the value ‘1’ is being passed to the -A option.
Oh, forgot to mention that we never had any apps configured in the older version. Just the ability to see your files and submit jobs. So we’d like to add some apps like Matlab, Jupyter Notebooks, RStudio, etc.
Would need to know how to do that. Also I was referencing this instruction:
auto_accounts will generate cluster aware lists if you have dynamic options enabled. This means it will only show a list of accounts available for the cluster that’s currently selected. If this setting is not enabled, it will generate a list of all accounts available on all clusters and will not hide any of them.
That implies that dynamic options needs to be enabled.
It’s a configuration if you follow that link. At OSC all our accounts work on all our clusters, but if you have some accounts that work for some clusters and so on, if you add that configuration then it’ll only show the accounts for the cluster that you’ve selected. so it’ll automatically toggle accounts that don’tt exist on the cluster that you’ve selected.
Again, you can find the exact sbatch command being issued in your log file. I would ask if your account selection list is actually populated and if you did in fact remove the account reference in the submit.yml.erb.
This is why it’s blank. auto_accounts and bc_account already know how to submit the account, so if you’re using one of those you don’t need this line at all.
If you’re using a user defined name like my_new_account_field, then you need to set it here.
accounting_id: "<%= my_new_account_field %>"
That’s why we provide auto_accounts and bc_account fields, so that you don’t have to provide them in the submit.yml - they do this automatically. On the other hand - if you define a completely new field - then you need to use it in submit.yml.
