-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there an exhaustive list of situations where N_PROF > 1? #16
Comments
The more specific part of this question related to why For reference, output of vertical sampling scheme variable: for i in range(nc.dimensions['N_PROF'].size):
# read_ncstr is my own function that makes netcdf string arrays more readable
print(read_ncstr(nc['VERTICAL_SAMPLING_SCHEME'][:].data[i,:]))
# Out:
# Primary sampling: averaged [2s sampling,1dbar average in [100-10]dbar;2s samp.,1dbar avg in [10-2.1]dbar]
# Near-surface sampling: averaged, unpumped [2s samp.,1dbar avg in [2.1-1]dbar;2s samp.,1dbar avg in [1dbar-surface]]
# Secondary sampling: mixed [10s sampling in [100-10]dbar;2s samp. in [10-1]dbar;10s samp.,1dbar avg in [1dbar-surface]]
# Secondary sampling: mixed [10s sampling in [100-10]dbar;2s samp. in [10-1]dbar;10s samp.,1dbar avg in [1dbar-surface]] |
N_PROF>1 will occur when:
If a descending and ascending profiles are collected during the same cycle, these profiles are in two separate files ( R[wmo][cycle].nc and R[wmo][cycle]D.nc , with 'D' for the descending profile), In this case, in each file, N_PROF=1, of course if there are no multiple sensors/sampling schemes or other "bouncing" profiles. I don't know if this answers your question... "Suppose a hypothetical float carries a high-resolution CTD sensor and a low-resolution nitrate sensor. In each single-cycle, this hypothetical float is configured to return a 2-dbar bin-averaged CTD profile to 1000 dbar with no corresponding nitrate measurements, and a discrete 250-dbar interval nitrate profile to 1000 dbar with no corresponding temperature and salinity measurements. The parameters in the resulting core-Argo and b-Argo profile files are formatted as follows for the two profiles in each cycle: |
Is your QC expertise request related to a problem? Please describe.
In a given cycle, the netCDF dimension
N_PROF
is typically 1 (1 cycle, 1 profile), but is sometimes greater than 1 (1 cycle, multiple profiles). In my experience, this is usually when there are observations recorded on the descent, and so there are two profiles for that cycle (files R[wmo]_[cycle].nc R[wmo]_[cycle]D.nc to give an example. There are some situations where there are even more than 2 profiles, and from the file I can't seem to discern from the file why that is (see next section for data). I also have not found an exhaustive lists in any Argo handbook, but hoping I just haven't been looking in the right place and someone could point me to a list or table.Describe the Argo data you'd like to validate
An example of such a file is here: https://data-argo.ifremer.fr/dac/coriolis/6901494/profiles/BD6901494_352.nc
Describe QC methods you've already considered
Not so much a QC method, but this is a more general question related to this issue in the argoFloats R package: ArgoCanada/argoFloats#413
Additional context
Some python code looking at the netCDF file:
Click to unroll code
The text was updated successfully, but these errors were encountered: