rachidelmimouni / imos-toolbox

Automatically exported from code.google.com/p/imos-toolbox
0 stars 0 forks source link

SBE56 #148

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi, have started using Seabird SBE56 temperature loggers so we need a new 
parser written. Example data is attached and contains raw data and 
exported/converted files using the default options.

SBE05609671207.xml : data downloaded from instrument
SBE05609671207.cnv : export as cnv, options date format "Julian Days" and 
"output informational header". Note there is also an option for date as 
"Seconds since 1-Jan-2000" if preferable.
SBE05609671207.csv : export as csv, options data format "yyyy-mm-dd" and 
"output informational header".
SBE05609671207.png : what the data should look like

As well as the informational header there is also an option "Output sample 
number" if required.

Thanks,
Simon.

Original issue reported on code.google.com by s.spag...@gmail.com on 22 Aug 2012 at 1:51

Attachments:

GoogleCodeExporter commented 9 years ago
Hi Guillaume, cobbled up something which I think works

1. copied SBE37SMParse.m to SBE56Parse.m, changed reference to 'SBE37' to 
'SBE56'. Done this purely because I couldn't get SBE37SMParse to pick up 
instrument_model properly. Note I could have become really confused at this 
point at it may be possible to tweak SBE37SMParse.m and put a line in 
instruments.txt to get SBE56 to use SBE37SM parser.
2. modified readSBE37cnv.m to include seaterm v2 names used for pressure 
'prdM', temperature 'tv290C', time in seconds since 01-Jan-2000 'timeK', 
conductivity 'cond0S/m'

So basically can confirm you have mostly everything already in the toolbox to 
handle SBE56's it just requires some cleaning up. Waiting for Paul Rigby to 
return from holidays to check over the netcdf file.

Original comment by s.spag...@gmail.com on 7 Sep 2012 at 2:45

Attachments:

GoogleCodeExporter commented 9 years ago
Just noticed had the wrong version of readSBE37cnv.m with wrong string to 
search for conductivity, should look like

% conductivity (S/m)
    case {'c0S0x2Fm', 'cond0S0x2Fm'} % 'c0S/m', 'cond0S/m'

And by extension can also add

        % conductivity (mS/cm)
        % mS/cm -> S/m
    case {'c0ms0x2Fcm', 'cond0mS0x2Fcm'}

and

        % conductivity (uS/cm)
    case {'c0us0x2Fcm', 'cond0uS0x2Fcm'}

Original comment by s.spag...@gmail.com on 27 Sep 2012 at 5:55

GoogleCodeExporter commented 9 years ago
Thanks for this Simon,

this will be included in the next toolbox version. I'll let you know when the 
next snapshot will include this so that you can test it.

Cheers,

Guillaume.

Original comment by guillaum...@gmail.com on 1 Oct 2012 at 2:28