pygeodyn issueshttps://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues2019-03-20T16:53:12+01:00https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/51Health check of results2019-03-20T16:53:12+01:00Loic HuderHealth check of resultsAdd a more viable health check of the results in test_run.py (use the Lowes spectra ?)Add a more viable health check of the results in test_run.py (use the Lowes spectra ?)Loic HuderLoic Huderhttps://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/68[Proposal] Set up linting in the CI2020-10-14T12:17:06+02:00Loic Huder[Proposal] Set up linting in the CIIt will help catching errors.
`pyflakes` would be my preferred candidate. `flake8` if we want formatting checks.
Note that !54 should be merged first.It will help catching errors.
`pyflakes` would be my preferred candidate. `flake8` if we want formatting checks.
Note that !54 should be merged first.https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/69The Ultimate Guide to Argumentative Essay Writing - 2021 Guide2021-09-06T10:02:43+02:00Ghost UserThe Ultimate Guide to Argumentative Essay Writing - 2021 Guide[The_Ultimate_Guide_to_Argumentative_Essay_Writing_-_2021_Guide.pdf](/uploads/8852a2844abc7634794252832cb09f0e/The_Ultimate_Guide_to_Argumentative_Essay_Writing_-_2021_Guide.pdf)[The_Ultimate_Guide_to_Argumentative_Essay_Writing_-_2021_Guide.pdf](/uploads/8852a2844abc7634794252832cb09f0e/The_Ultimate_Guide_to_Argumentative_Essay_Writing_-_2021_Guide.pdf)https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/70Adding the possibility to export calculated data every n step2024-03-29T13:55:10+01:00Romain ClaveauAdding the possibility to export calculated data every n stepAs crashes may occur during calculations, it would be a good idea to allow for data exportation every n step (e.g. every analysis step)As crashes may occur during calculations, it would be a good idea to allow for data exportation every n step (e.g. every analysis step)https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/71Failed to retrieve GVO observations when dealing when using forecast timestep...2024-03-29T14:04:25+01:00Romain ClaveauFailed to retrieve GVO observations when dealing when using forecast timestep of 1 monthCurrently, observations are detected within an interval t +- dft / 2. However, GVO times aren't rounded (e.g. 2000.08333, end of January). Two possibilities :
- Measures are done at the end of January
- Decimal part exists because of a b...Currently, observations are detected within an interval t +- dft / 2. However, GVO times aren't rounded (e.g. 2000.08333, end of January). Two possibilities :
- Measures are done at the end of January
- Decimal part exists because of a bad conversion of the timestamp into years
Until we have an answer to this question, it is sufficient, given that dtf >= 1 month, that we put t +- 0.1 instead of dtf / 2 as a temporary fix.https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/72External dense SWARM error matrix being loaded even if dta != 4 months2024-03-29T14:18:05+01:00Romain ClaveauExternal dense SWARM error matrix being loaded even if dta != 4 monthsCurrently, we can specify pygeodyn to use the SWARM error matrix stored as R_dense_swarm.txt inside data/observations/GOVO/SWARM_err/
However, it is calibrated only every-4-months observations and should be used only with an analysis ti...Currently, we can specify pygeodyn to use the SWARM error matrix stored as R_dense_swarm.txt inside data/observations/GOVO/SWARM_err/
However, it is calibrated only every-4-months observations and should be used only with an analysis timestep of 4 months. However, the matrix is still loaded even if timestep != 4 months, as long as we specify SW_err str dense in the configuration file.
A possibility would be to flag out when we are trying to use this dense matrix with inappropriate timestep, and automatically switch to a diagonal matrix.https://gricad-gitlab.univ-grenoble-alpes.fr/Geodynamo/pygeodyn/-/issues/73Impossible to launch calculations with 0path priors2024-03-29T14:27:47+01:00Romain ClaveauImpossible to launch calculations with 0path priorsCurrently, it is not possible to launch calculations with 0path priors because the associated files do not store timestamps. As a result, the function `read_0_path` sets `times = [None]` leading pygeodyn to crash.
A workaround would be ...Currently, it is not possible to launch calculations with 0path priors because the associated files do not store timestamps. As a result, the function `read_0_path` sets `times = [None]` leading pygeodyn to crash.
A workaround would be to create an array, with a given timestep, whose length match that of data.