Are you using the terms CryoSPARC scheduler and _CryoSPARC master interchangeably?
In the simplest case, the Linux account that runs CryoSPARC can submit an LSF job by running bsub on the computer that also runs cryosparc_master processes.
At minimum, the CryoSPARC master and LSF compute nodes should share
a Linux account that runs CryoSPARC processes, with matching user ids.
write access to shared storage for project directories
a common path to each project directory
It may simplify the configuration if the CryoSPARC master computer can directly submit LSF jobs, as mentioned earlier.
Are you using the terms CryoSPARC scheduler and _CryoSPARC master interchangeably?
Yes sorry for that “Cryosparch scheduler”
In the simplest case, the Linux account that runs CryoSPARC can submit an LSF job by running bsub on the computer that also runs cryosparc_master processes.
No that is not the case but I can create a consistent accounts arcoss the node “cryosparc”
At minimum, the CryoSPARC master and LSF compute nodes should share
a Linux account that runs CryoSPARC processes, with matching user ids.
write access to shared storage for project directories
a common path to each project directory
Ok will configure
It may simplify the configuration if the CryoSPARC master computer can directly submit LSF jobs, as mentioned earlier.
I am not sure right now that there is. If there were a way, however, would not this result in inconsistencies in file ownerships between files created inside the job directories on the master on one hand (job directory created), worker (processing output) on the other?