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 1: | Line 1: | ||
'''Under Construction''' |
|||
This is rough outline of the subrounties that need to be changed to add a new model to GMIN. |
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. |
Your mileage will vary a bit with respect to the details. |
||
| Line 7: | Line 9: | ||
'''keyword.f''' -- reads ''pathdata'' |
'''keyword.f''' -- reads ''pathdata'' |
||
'''setup.f''' -- reads points.min, points.ts, extractedts |
'''setup.f''' -- reads points.min, points.ts, extractedts, calculates moments of interia |
||
'''connectodata.f''' -- print out start.<n>, finish.<n>, odata.connect.<n> |
'''connectodata.f''' -- print out start.<n>, finish.<n>, odata.connect.<n> |
||
Revision as of 09:38, 8 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
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)