In the current MAST–StructOpt interface, users must run mast at least every generation. Normally this is not an issue if the user is evaluating the structures using VASP as the energy calculations will take a long time and so the actual running of mast is not overly burdening. However, if the user is only submitting relatively short LAMMPS calculations to queue each generation, then running mast continuously can be a pain. In development is a version of running mast specified by including ‘LOOPED’ in the calc_method parameter that loops over generations internally and can reduce the burden of calling mast. The trouble with this is that the queue submissions need to be performed on the head node. The current solution is to ssh to the head node from the compute node to submit the new job. However, this may require user passwords and user names on some systems.
In the current MAST–StructOpt interface, users must run mast at least every generation. Normally this is not an issue if the user is evaluating the structures using VASP as the energy calculations will take a long time and so the actual running of mast is not overly burdening. However, if the user is only submitting relatively short LAMMPS calculations to queue each generation, then running mast continuously can be a pain. In development is a version of running mast specified by including ‘LOOPED’ in the calc_method parameter that loops over generations internally and can reduce the burden of calling mast. The trouble with this is that the queue submissions need to be performed on the head node. The current solution is to ssh to the head node from the compute node to submit the new job. However, this may require user passwords and user names on some systems.