AMISOR MOORING DATA -------------------------- All these data remain the property of the ACE CRC (Antarctic Climate and Ecosystems Cooperative Research Centre). The ACE CRC aims to deliver knowledge and information needed by our diverse research users. To assess our effectiveness, we need to keep track of data use by you and others. Thus, if you receive this data set, please send an email to: mark.rosenberg@utas.edu.au with the following information: 1. your name and institution 2. what you plan to use the data for (a brief sentence is sufficient) examples: analysing mixed layer nutrient levels for a PhD thesis preparing a Southern Ocean climatology for general research looking at ocean circulation for a conference presentation The data originators (ACE CRC, Australia) should be acknowledged in any publication, including internal reports, published reports, journal articles, presentations etc. For this data set please use the reference: Rosenberg, M., Bindoff, N., Curran, C., Helmond, I., Miller, K., McLaughlan, D., Church, J., Richman, J., and Leffanue, H. (2002) Amery Ice Shelf Experiment (AMISOR) - marine science cruises AU0106 and AU0207 - oceanographic field measurements and analysis. Antarctic Cooperative Research Centre, Research Report No. 30, September 2002, Hobart, Australia, 119 pp. Please include this README file if you pass the data on to anyone else. Thanks very much for your help. regards, Mark Rosenberg mark.rosenberg@utas.edu.au ------------------------------------ These files contain mooring data from the AMISOR Experiment deployments (ship-based component). The data report (bigam.doc) contains a full description of moorings and data processing information. Important data quality information is included in the report. Please delete any previous versions you have of the data, and replace with these final versions. ASCII FORMAT ------------ For all ascii format data files, note the following: * -999 is a null value * recording interval is not regular, as times have been linearly "stretched" or "compressed" over the year to account for clock error * there's a line of data for each ~x minute record, where x is the recording interval (i.e. no time gaps) * for amisor9, the mooring was deployed at location A, with position 68deg. 33.693'S , 72deg. 42.297'E in water depth 544 m. On 07/05/2001, an iceberg dragged the mooring ~2 miles to the NW to the new location B in water depth 629 m. All the station info in amisor9.mat is for position B. 1. Microcat and SBE39 files: the files cat*.dat contain a 13 line header, followed by column formatted data as follows, for the SeaBird SBE37 microcats: column parameter 1 decimal time, from midnight on December 31st 2000, where, for example, midday on 1st Jan 2001 = decimal time 0.5 (UTC) 2 temperature (degrees C, ITS90) 3 conductivity (mS/cm) 4 salinity (PSS78) 5 day (all times UTC) 6 month 7 year 8 hour 9 minute 10 second the files sbe*.dat contain a 13 line header, followed by column formatted data as follows, for the SeaBird SBE39 temperature recorders: column parameter 1 decimal time, from midnight on December 31st 2000, where, for example, midday on 1st Jan 2001 = decimal time 0.5 (UTC) 2 temperature (degrees C, ITS90) 3 day (all times UTC) 4 month 5 year 6 hour 7 minute 8 second 2. Aanderaa RCM current meter data the files rcm*.dat contain a 14 line header, followed by column formatted data as follows, for Aanderaa RCM5 and RCM8 rotor-type current meters: column parameter 1 decimal time, from midnight on December 31st 2000, where, for example, midday on 1st Jan 2001 = decimal time 0.5 (UTC) 2 year (all times UTC) 3 month 4 day 5 hour 6 minute 7 current speed (cm/sec) 8 current direction (degrees true), towards which current is flowing 9 u=E/W current component (cm/sec), where +ve is east 10 v=N/S current component (cm/sec), where +ve is north 11 pressure (dbar) 12 temperature (degrees C) 13 conductivity (mS/cm) * for aanderaas in general, temperature and pressure data should only be used qualitatively. For accurate T and S data refer to microcats and sbe39's * pressure data for 10867, 10868 and 10869 is bad. * pressure data for some other aanderaas may be very inaccurate * Aanderaa RCM9 acoustic current meter serial 597 has the same format as above, with the additional column 14 containing turbidity (NTU) data 3. Station information Station information is summarised in the file station.dat MATLAB FORMAT ------------- * for all matlab data, null values are represented by NaN * as above, there are no time gaps 1. Microcat, SBE39, 9311 and RCM8 data The data are in matlab files amisorx.mat, where x=mooring number. For the matlab vectors, cat=SBE37 microcat rcm=Aanderaa rotor-type current meter sbe=SBE39 temperature recorder For the various instruments: cond = conductivity (mS/cm) d = instrument deployment depth (m) date = ddmmyyyy date (UTC) dectime = decimal time from midnight on December 31st 2000. So, e.g. midday on January 1st 2001=0.5 decimal time (UTC) dir = current direction (degrees true), towards which current is flowing p = instrument deployment pressure (dbar) press = instrument pressure data (dbar) sal = salinity (PSS78) spd = current speed (cm/s) temp = temperature (deg.C, ITS90) time = hhmmss time (UTC) turb = turbidity (NTU) u = E/W current component (cm/s, +ve towards the east) v = N/S current component (cm/s, +ve towards the north) lat and lon = latitude and longitude (degrees) for each mooring botd = ocean depth (m) for each mooring 2. moored ADCP data Moored ADCP data from RDI 150 kHz ADCP's are contained in the matlab files d0135new.mat (at mooring 6), d0136new.mat (at mooring 4), and d1136new.mat (at mooring 5). ADCP 1143 at mooring 7 failed to collect data. The matrices and vectors in the files are (where xxxx=adcp number e.g. 0136): dxxxx_amp1=echo amplitude (in counts) for beam 1 dxxxx_amp2=echo amplitude (in counts) for beam 2 dxxxx_amp3=echo amplitude (in counts) for beam 3 dxxxx_amp4=echo amplitude (in counts) for beam 4 dxxxx_avbeamcor=average beam correlation (counts) dxxxx_bindep=depth (m) (from surface) to centre of each vertical bin dxxxx_dectime=decimal time (UTC) (decimal days from midnight on December 31st 2000; so e.g. midday on Jan. 1st 2001=0.5 decimal time; midday on Jan 1st 2002 =365.5 decimal time) dxxxx_dir=current direction (deg. true, towards which current is flowing) dxxxx_ensemble=ensemble number dxxxx_errv=RMS error velocity (cm/s) dxxxx_heading=instrument heading (deg. true) - not to be confused with current direction dxxxx_orien=instrument orientation flag dxxxx_pcntgd4=average percentage of 4 beam solutions used in making the bin dxxxx_pitch=pitch (deg.) of instrument dxxxx_roll=roll (deg.) of instrument dxxxx_spd=current speed (cm/s) dxxxx_temp=temperature (deg.C) dxxxx_u=E/W current component (cm/s, +ve towards the east) dxxxx_v=N/S current component (cm/s, +ve towards the north) dxxxx_w=vertical velocity (cm/s, +ve upwards) Note the following for the ADCP data: * rows 1 to 40 in all matlab matrices and vectors correspond to vertical bins 40 to 1 (i.e. row 40 = bin 1, which is the deepest bin for an ADCP which is looking upwards) * all currents are in earth co-ordinates (i.e. absolute current values) * recording interval is not regular, as times have been linearly "stretched" over the year to account for clock error The following quality control has been done: * if pcntgd4 < 80%, bin is flagged as bad * if avbeamcor < 70, bin is flagged as bad * bins 35 to 40 of each ensemble are flagged as bad, due to side lobe contamination * if orien=0, the entire ensemble is flagged as bad In the case of the ADCP matlab files, flagging bins/ensembles as bad means changing the spd, dir, u and v bins/ensembles to NaN (i.e. data removed).