Difference between revisions of "To Do"
From CometWiki
m (Created page with '*XML import/export format. **At the moment, if we change the load/save code to add a variable etc, the save file format changes so we can't load old datasets. Current workarou...') |
m |
||
| Line 1: | Line 1: | ||
*XML import/export format. | *XML import/export format. | ||
| − | **At the moment, if we change the load/save code to add a variable etc, the save file format changes so we can't load old datasets. Current workaround is to check the date of the old data and temporarily revert to that version of the code in the git repository. A proper fix would be to have a separate XML save format that | + | **At the moment, if we change the load/save code to add a variable etc, the save file format changes so we can't load old datasets. Current workaround is to check the date of the old data and temporarily revert to that version of the code in the git repository. A proper fix would be to have a separate XML save format that also contains the names of the variables, so that future changes don't break the load/save. |
*Xgrid | *Xgrid | ||
**Given the importance of running the program on a cluster, it would be nice to use [http://www.apple.com/server/macosx/technology/xgrid.html Apple's Xgrid] | **Given the importance of running the program on a cluster, it would be nice to use [http://www.apple.com/server/macosx/technology/xgrid.html Apple's Xgrid] | ||
Latest revision as of 07:50, 14 April 2009
- XML import/export format.
- At the moment, if we change the load/save code to add a variable etc, the save file format changes so we can't load old datasets. Current workaround is to check the date of the old data and temporarily revert to that version of the code in the git repository. A proper fix would be to have a separate XML save format that also contains the names of the variables, so that future changes don't break the load/save.
- Xgrid
- Given the importance of running the program on a cluster, it would be nice to use Apple's Xgrid
