These files are various definition files for using GEOSfvdycore and GEOSgcm within Singularity. Most are on the Singularity library. There are constant changes to GEOS, so these may not build because of that.
Files ending in:
b.def : Indicates the container that installs the base libraries
fvy.def : Indicates the container that installs GEOSfvdycore
gcm.def : Indicates the container that installs GEOSgcm
When using the containers for GEOSfvdycore and GEOSgcm, the install directories are located at /GEOSfvdycore and /GEOSgcm inside their containers respectively. Documentation for running GEOSgcm can be found at the GEOS-5 wiki. Running GEOSfvdycore is a similar process.
You go to /installdirectory/install/bin for one of them, and then use their setup scripts to create an experiment directory. GEOSfvdycore has fv3_setup and GEOSgcm has gcm_setup. If you want to run an experimental directory you made with slurm and singularity, you can create a slurm script and use something like:
singularity exec image.sif experimentdirectory/./fv3.j
You should convert your .sif file to a sandbox and use that for each run, especially if you use a container multiple times.
singularity build -s yoursandbox/ yourimage.sif
Now you can use that sandbox for runs instead of the image. This will save time in converting the image and having to clean it. You do not need the original .sif file for the sandbox.
If you want to change the amount of tasks the run script specifies or use multiple nodes, then yes. A specified amount of tasks (ntasks) will already be made once an experiment directory is created, and you should ideally go by these conditions for your slurm script. However, if you'd like to change these values, the variables FV_NX and FV_NY in the runscript will have to be changed to what number of nodes / number of cores you'd like.