Difference between revisions of "Adding a model for PATHSAMPLE"
Jump to navigation
Jump to search
import>Mp466 |
import>Mp466 |
||
| Line 9: | Line 9: | ||
'''keyword.f''' -- reads ''pathdata'' |
'''keyword.f''' -- reads ''pathdata'' |
||
| − | '''getnewpath.f''' -- reads '' |
+ | '''getnewpath.f''' -- reads ''path.info'' |
| + | '''submitoptimjob.f''' -- moves start.CONNSTR2 start.CONNSTR1 |
||
'''getallpaths.f''' -- reads ''path.info'', ''min.data.info'', |
'''getallpaths.f''' -- reads ''path.info'', ''min.data.info'', |
||
Revision as of 23:43, 10 July 2008
Under Construction
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
keyword.f -- reads pathdata
getnewpath.f -- reads path.info
submitoptimjob.f -- moves start.CONNSTR2 start.CONNSTR1
getallpaths.f -- reads path.info, min.data.info,
setup.f -- reads points.min, points.ts, extractedts, calculates moments of interia
connectodata.f -- print out start.<n>, finish.<n>, odata.connect.<n>
--mp466 00:24, 8 July 2008 (BST)