Base implementation of Parquet file writing#2583
Base implementation of Parquet file writing#2583VeckoTheGecko merged 35 commits intoParcels-code:mainfrom
Conversation
1d26f4a to
91ce496
Compare
|
@erikvansebille let's table some of these questions for our meeting tomorrow (mainly around datetime serialization in the Parquet file) |
Covered by test_write_dtypes_pfile
for more information, see https://pre-commit.ci
e06a618 to
60ceef6
Compare
Remove temporary test_cftime.py file
This function is now independent of the time_interval as time is now stored as float
Remove nested key - save on root instead
60ceef6 to
54c829a
Compare
|
@erikvansebille I moved |
|
(we'll likely get doc failures on this PR - which is to be expected since they haven't been updated) |
erikvansebille
left a comment
There was a problem hiding this comment.
Very nice work. And as I'm going through updating all the documentation, it seems to work smoothly too!
A few small comments below
| @@ -187,7 +154,7 @@ def test_variable_written_once(): | |||
| @pytest.mark.skip(reason="Pending ParticleFile refactor; see issue #2386") | |||
There was a problem hiding this comment.
Does this test work again? If not out of the box, perhaps we should discuss what we actually expect from output of a looped pset.execute...
There was a problem hiding this comment.
This test was introduced in 4b28ddb . I'm ok cutting tests that are no longer valuable (/tested specific implementation bugs from the old codebase). I don't really understand this test - do you think its still valuable?
perhaps we should discuss what we actually expect from output of a looped pset.execute...
Agreed. Should we open a tracking issue? Whatever we decide on that front we can add separate tests
There was a problem hiding this comment.
Yes, I think it is a valuable test (as it tests what happens in the particle file when pset.execute() is run in a for-loop). But perhaps better for a later PR
There was a problem hiding this comment.
And perhaps rename from test_pset_repeated_release_delayed_adding_deleting - since I find that quite confusing
61430c9 to
6695187
Compare
a5bdd31 to
3c52647
Compare
Description
This PR introduces Parquet file writing to Parcels.
I still need to work on:
parcels.read_particlefile(...)to streamline ingestion into cftime objects.test_particlefile.pyfile - are there tests that are no longer needed? What would be the best testing approach here?Posting as draft for initial feedback
Checklist
mainfor normal development,v3-supportfor v3 support)AI Disclosure