Difference between revisions of "Ensure software is usable by Mimi Tzeng"

From Geoscience Paper of the Future
Jump to: navigation, search
(Set PropertyValue: Progress = 80)
Line 20: Line 20:
 
<li>pdfsam (or other PDF concatenator)</li>
 
<li>pdfsam (or other PDF concatenator)</li>
 
<li>MS Word</li></ul>
 
<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.
 +
 +
 +
  
 
<!-- Add any wiki Text above this Line -->
 
<!-- Add any wiki Text above this Line -->

Revision as of 18:40, 4 March 2015


Details on how to do this task: Ensure software is usable

  • Data to be used: FOCAL mooring from 20110413_20110518
  • Software for CTDs and Thermisters:
    • SeaTerm
    • SBE Data Processing
    • EcoWatch (for YSI)
    • perl
    • any text editor
    • Matlab
    • pdfsam (or other PDF concatenator)
    • MS Word
  • Software for ADCP:
    • 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.