#2482: Inconsistency in Simfactory submission scripts
| Reporter: | Steven R. Brandt |
| Status: | new |
| Milestone: | |
| Version: | |
| Type: | bug |
| Priority: | major |
| Component: | SimFactory |
Comment (by Roland Haas):
I added your sbrandt XSEDE account to my allocations on Bridges, Stampede2 and Comet.
TACC uses 2 factor authentication of their own making. . You have to first obtain a password for you TACC account from: https://portal.tacc.utexas.edu/password-reset which will offer to set up TACC's two-factor-authentication. You can try using TACC's own app or the Google Authenticator for Android or iOS (only tested with Android so far). Whenever you use simfactory you must (well if you want to use the Skylake nodes and not the Knight’s landing ones) pass a --machine stampede2-skx option to it to ensure that the "Skylake" section of the Stampede2 is used and not the "Knights landing one". Alternative
you can create a file $HOME/.hostname on Stampede2 and put the text stampede2-skx in it. This will cause simfactory to use the skylake section by default. If you are on multiple XSEDE allocations on stampede2 you can use the --allocation option of simfactory to select which one to charge.
You may have to wait for 1-2 business days for your $HOME to be created and logging in earlier may result in you being dropped to / with a message along the lines “you do not exist” if you are unlucky. This fixes itself once $HOME exists.
--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2482/inconsistency-in-simfactory-submission