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

pyLipd integration into tutorials #23

Closed
CommonClimate opened this issue Apr 4, 2023 · 1 comment · Fixed by #49
Closed

pyLipd integration into tutorials #23

CommonClimate opened this issue Apr 4, 2023 · 1 comment · Fixed by #49
Assignees

Comments

@CommonClimate
Copy link
Contributor

L1_working_with_LiPD.ipynb should be updated to reflect pyLipd updates, when the latter are ready for prime time.

Note: Euro2k example can go either there or in the MSES tutorial

@khider
Copy link
Member

khider commented May 8, 2023

Going from LiPD to Series/GeoSeries/MulitpleGeoSeries. Need to move the functions supported by LiPD/LiPD Series to the classes:

  • LiPD:

  • to_tso: No longer needed since we do not deal exclusively with LiPD

  • to_LipdSeries: Creates a LiPDSeries from the object. An equivalent function would be MultipleSeries -> Series

  • to_LipdSeriesList: Extracted all available series to create a MultipleSeries object. No longer needed

  • extract: This was mostly internal and allowed to get the information contain at the LiPD level (ensembles) to the timeseries level (variables)

  • mapAllArchive : Maps per archive. The underlying function takes a criteria parameter (i.e., archive) but would leave the work to find the values to a user. With MultipleGeoSeries, we could create a parameter that makes this map by archive or elevation...

  • LiPDSeries:

  • chronEnsembletoPaleo: Should be independent function that would also allow to take Series and tables from other file format

  • map : Creates a map - Now should be in GeoSeries

  • getMetadata: Internal function to get relevant metadata for the dashboard. Would need full LiPD information

  • dashboard: Can be attached to GeoSeries if we remove metadata dependency. The question is how to do the ensemble version - create a dashboard function for EnsembleGeoSeries

  • mapNearRecord: Would need a complimentary MultipleGeoSeries object to work

  • plot_age_depth : Remove from Pyleoclim

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants