-
Currently I am writing extremely small files (say 'file.nc') (11 particles at 11 time steps). Nevertheless, the written files are 45 Mb each.
I can create a file with fixed dimensions, with a size…
-
The old website had a 'parcels documentation' tab, sorted by topic and with links to fragments of the source code. It was not properly updating with the releases and was quite ugly, however it offered…
-
Hello,
I am trying to use parcels on a tri-pole POP grid. What is the best way to set up the mesh option in feild.from_data? The data I have includes corrections angles for u and v near the poles. …
-
The source code for `FieldSet.from_nemo` on does not match .
It looks like the HTML files in oceanparcels.org/_modules are outdated.
-
_(My example is for adding Stokes drift to the ocean velocities used for advecting particles. The general idea of combining velocity fields in a non-invasive way is very interesting for various appli…
-
Hello Erik and Phillipe,
I run Parcels with 1/12° global currents and my velocity data are so big that I feel convenient to extract a subdomain of velocity fields to work with. But some of the dri…
-
In the new parcels version the field.advancetime() was replaced by loading a list of fields in the beginning, but these fields are according to @delandmeterp created in the particle execution. For a …
ghost updated
6 years ago
-
Hi,
It seems that the compiler (JIT) is broken for Windows. A simple script with `AdvectionRK4` shows an error: `ValueError: unable to map dtype 'uint64'`.
I have tested in Windows 10 and in Ub…
-
Currently, defines a dimension `trajectory` and a variables `trajectory` that has more than one dimension. This collides with the concept of "coordinate variables" defined in [the CF conventions](ht…
-
Hi,
it seems like printing a local kernel variable does not work for JIT particles. While it works in ScipyMode, casting the function
```python
def Print1(particle,fieldset,time,dt):
h = 1
…