Difference between revisions of "Ensure software is usable by Mimi Tzeng"
(Set PropertyValue: Type = low) |
(Set PropertyValue: Progress = 100) |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
[[Category:Task]] | [[Category:Task]] | ||
<br/><b>Details on how to do this task:</b> [[Ensure software is usable]]<br/><br/> | <br/><b>Details on how to do this task:</b> [[Ensure software is usable]]<br/><br/> | ||
| + | |||
| + | <li>Data to be used: FOCAL mooring from 20110413_20110518</li> | ||
| + | |||
| + | <li>Software for CTDs and Thermisters: </li> | ||
| + | <ul><li>SeaTerm</li> | ||
| + | <li>SBE Data Processing</li> | ||
| + | <li>EcoWatch (for YSI)</li> | ||
| + | <li>perl</li> | ||
| + | <li>any text editor</li> | ||
| + | <li>Matlab</li> | ||
| + | <li>pdfsam (or other PDF concatenator)</li> | ||
| + | <li>MS Word</li></ul> | ||
| + | |||
| + | <li>Software for ADCP:</li> | ||
| + | <ul><li>WinADCP</li> | ||
| + | <li>Matlab</li> | ||
| + | <li>any text editor</li> | ||
| + | <li>pdfsam (or other PDF concatenator)</li> | ||
| + | <li>MS Word</li></ul> | ||
| + | |||
| + | Software seems to come in two forms:<br> | ||
| + | A) the off-the-shelf professionally-produced kind that most people think of upon seeing the word "software"<br> | ||
| + | B) the highly specific custom-made scripts that automate particular tasks for a particular lab or other working group, generally intended for internal use. | ||
| + | <br><br> | ||
| + | The list above is for software of type A.<br> | ||
| + | Software of Type B for this project are in the form of several Matlab and perl scripts. These are gathered together in a folder; they don't have names that will mean anything to anyone else, and so they aren't listed here. | ||
| + | <br><br> | ||
| + | Task completion: I am waiting for Matlab to be reinstalled on the PI's lab computer so that I can rerun the entire processing to make sure that everything still works as intended. I am 95% confident that all will be fine, but won't claim that the "ensure software is usable" task is 100% complete until I can do this. | ||
| + | |||
| + | Update 20 Mar 2015: Today the PI got around to putting Matlab on his lab computer. I'm now much less confident that all will be fine, because the version of Matlab I used originally was (probably) from 2010, and the current version on the new PI's lab computer is 2015. Matlab has an annoying habit of changing things around between versions so that all previous scripts break in really stupid and time-consuming ways. I've already found two subtle differences (one of them will require a minor change in my perl script), and will have to look through the rest in more detail. | ||
| + | |||
| + | |||
<!-- Add any wiki Text above this Line --> | <!-- Add any wiki Text above this Line --> | ||
<!-- Do NOT Edit below this Line --> | <!-- Do NOT Edit below this Line --> | ||
| − | {{#set:| | + | {{#set: |
| + | Expertise=Open_science| | ||
| + | Expertise=Geosciences| | ||
| + | Owner=Mimi_Tzeng| | ||
| + | Progress=100| | ||
| + | StartDate=2015-02-07| | ||
| + | TargetDate=2015-02-20| | ||
Type=Low}} | Type=Low}} | ||
Latest revision as of 21:13, 1 July 2015
Details on how to do this task: Ensure software is usable
- SeaTerm
- SBE Data Processing
- EcoWatch (for YSI)
- perl
- any text editor
- Matlab
- pdfsam (or other PDF concatenator)
- MS Word
- WinADCP
- Matlab
- any text editor
- pdfsam (or other PDF concatenator)
- MS Word
Software seems to come in two forms:
A) the off-the-shelf professionally-produced kind that most people think of upon seeing the word "software"
B) the highly specific custom-made scripts that automate particular tasks for a particular lab or other working group, generally intended for internal use.
The list above is for software of type A.
Software of Type B for this project are in the form of several Matlab and perl scripts. These are gathered together in a folder; they don't have names that will mean anything to anyone else, and so they aren't listed here.
Task completion: I am waiting for Matlab to be reinstalled on the PI's lab computer so that I can rerun the entire processing to make sure that everything still works as intended. I am 95% confident that all will be fine, but won't claim that the "ensure software is usable" task is 100% complete until I can do this.
Update 20 Mar 2015: Today the PI got around to putting Matlab on his lab computer. I'm now much less confident that all will be fine, because the version of Matlab I used originally was (probably) from 2010, and the current version on the new PI's lab computer is 2015. Matlab has an annoying habit of changing things around between versions so that all previous scripts break in really stupid and time-consuming ways. I've already found two subtle differences (one of them will require a minor change in my perl script), and will have to look through the rest in more detail.
