Skip to content
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

Issues with DataSet fetched from Argopy for Indian Ocean region #87

Closed
mayursapkal opened this issue May 7, 2021 · 5 comments
Closed
Labels
invalid This doesn't seem right question Further information is requested

Comments

@mayursapkal
Copy link

mayursapkal commented May 7, 2021

Hello, Argopy!
I began working on a classification problem in the beginning of this year, using Argo data as input.
Since the project is based on the Indian Ocean, I used Argopy's Parallel data fetching method to obtain data from 2010 to 2019, ranging from 0 to 1000 dbar.
Data was fetched every two years, and then I used Xarray to merge all of the files.
I had a lot of problems using that data because the data was not handled/stored correctly within in the array.
The Issues are;

  1. Variables values not in sorted manner.
    Eg. variables values (Pressure, Temp, Salinity) in most of the arrays started with from 500 dbar values and respective to those Temperature and salinity values also stored in arrays.
    Screenshot (92)_LI

  2. Pressure values starting with negative values.
    Screenshot (96)_LI

  3. Only single value in whole DataArray.
    Screenshot (97)

  4. Unsuited Values
    Screenshot (98)

  5. Partial values for work, when fetched up to 1000 dbar level
    Screenshot (99)_LI

@quai20
Copy link
Member

quai20 commented May 10, 2021

Hi @mayursapkal ,
can you give me some examples of float and cycle numbers so I can check on my side ?
Also, which data source do you use ? erddap ? local_ftp ?
Cheerz

@mayursapkal
Copy link
Author

mayursapkal commented May 11, 2021

Hi @quai20,
Sorry for late reply. I've attached a screenshot of some of the Floats that have the above issue, and I tried to fix the problem on my own because I was short on time at the time of my project (link) .

  1. WMO float identifier : A9IIIII-
    image
    image

Data source I used was erddap. Please don't forgot to convert 1D array data to 2D array.

@gmaze
Copy link
Member

gmaze commented Sep 1, 2021

Hi @mayursapkal
Could you please show us the command used to fetch and process the data used in notebook linked to your previous message ?

1- I suspect this is due to the point2profile transformation
2- Using vertical-index averaging throughout all profiles in the notebooks will mix a lot of very different pressures and could explain the weird figures

@gmaze gmaze added invalid This doesn't seem right question Further information is requested labels Sep 7, 2021
@github-actions
Copy link

github-actions bot commented Dec 7, 2021

This issue was marked as staled automatically because it has not seen any activity in 90 days

@github-actions github-actions bot added the stale No activity over the last 90 days label Dec 7, 2021
@gmaze gmaze removed the stale No activity over the last 90 days label Sep 23, 2022
@gmaze
Copy link
Member

gmaze commented Sep 23, 2022

Closing because of a lack of information

@gmaze gmaze closed this as completed Sep 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
invalid This doesn't seem right question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants