Skip to content
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

Add clear instructions on how to *run* QCG pilot jobs and configure them #232

Open
djgroen opened this issue Jun 27, 2023 · 1 comment
Open
Assignees
Labels

Comments

@djgroen
Copy link
Owner

djgroen commented Jun 27, 2023

Suggestion on the FabSim3 documentation

Provide a clear and concise description of what is missing or what you need to be added in the FabSim3 documentation

@djgroen djgroen added the bug label Jun 27, 2023
@djgroen djgroen added this to the SEAVEAtk Release III milestone Jun 27, 2023
@djgroen djgroen self-assigned this Jun 27, 2023
@sweetmixture
Copy link

@arindamsaha1507 and I found it on Archer2 when PILOT_JOB is used, the default 'cray-python' module could clash with user's miniconda environment (invoking h5py not found error while running FabUQCampaign with PILOT_JOB mode). This could be solved by commenting out the 'cray-python' loading line in machine.yml.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants