Adding a model for PATHSAMPLE: Difference between revisions
Jump to navigation
Jump to search
import>Mp466 No edit summary |
import>Mp466 No edit summary |
||
| Line 2: | Line 2: | ||
Your mileage will vary a bit with respect to the details. |
Your mileage will vary a bit with respect to the details. |
||
OPTIM needs to output the necessary files ( |
OPTIM needs to output the necessary files (min.data.info from '''geopt.f''', path.info. '''CONNECT/ncutils.f90''') and they need to be named properly |
||
Revision as of 23:21, 7 July 2008
This is rough outline of the subrounties that need to be changed to add a new model to GMIN. Your mileage will vary a bit with respect to the details.
OPTIM needs to output the necessary files (min.data.info from geopt.f, path.info. CONNECT/ncutils.f90) and they need to be named properly
connectodata.f -- print out start.<n>, finish.<n>, odata.connect.<n>