Comment (by Roland Haas):

Oh, I see. Ok that is easier to offer suggestions for. There are two things that come mind.

1. I would try and make sure that simfactory recognizes thornyflat by checking that ./simfactory/bin/sim whoami returns thornyflat and that the mdb entry simfactory uses is the one I expect using ./simfactory/bin/sim print-mdb-entry $(./simfactory/bin/sim whoami | cut -d' ' -f3)
2. there seems to be a typo in the file name for the submit script. Namely it is called thornyflay.sub (a y where it should be t). This could prevent simfactory from finding it.

Are there any warnings when you start compiling a configuration? Sometimes simfactory picks a “default” run script when it cannot find the one specified on the command line or in the machine file

Just to be sure: you tried this compiling a fresh configuration, ideally after a rm -rf configs to make sure there are no lingering old files (a --reconfig does not overwrite an existing RunScript file in configs/sim)?

The submitscript attached to the ticket does already use --machine @MACHINE@ which makes sure that simfactory uses the correct machine description when executing the run script.

Note: looking at you file thornyflat.ini in the ticket there is a missing [thornyflat] that should be at the top of the file and that actually tells simfactory the name of the machine (the ini file section).

--
Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2598/thornyflat-production-run-segmentation