You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common issue with users is that when we want to run the same problem with different networks, we sometimes forget to do a make clean between builds. For some combination of networks, the build still works, but it is not clear what the executable will be doing.
One way to prevent this is to add the network name to the executable. Then the build directories in tmp_build_dir will also be separate and no make clean would be needed to switch networks.
I think that networks are unique among the microphysics in something that we change frequently within a problem setup.
Comments welcomed.
The text was updated successfully, but these errors were encountered:
A common issue with users is that when we want to run the same problem with different networks, we sometimes forget to do a
make clean
between builds. For some combination of networks, the build still works, but it is not clear what the executable will be doing.One way to prevent this is to add the network name to the executable. Then the build directories in
tmp_build_dir
will also be separate and nomake clean
would be needed to switch networks.I think that networks are unique among the microphysics in something that we change frequently within a problem setup.
Comments welcomed.
The text was updated successfully, but these errors were encountered: