-
|
Dear Community, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 12 replies
-
|
Dear @micgros, thanks for asking this question. We don't use ROMS output in my team here so Im not sure I can help. But I can imagine that it would be easier to advise you if you also provide the code you now use to create a FieldSet, and explain what goed wrong. Why does your code not work? |
Beta Was this translation helpful? Give feedback.
-
|
Ah, perhaps then add the following? indices = {'lon': range(455), 'lat': range(271)}
fieldset = FieldSet.from_c_grid_dataset(filenames, variables, dimensions, indices=indices) |
Beta Was this translation helpful? Give feedback.
-
|
Hi Erik, many thanks! It worked!! However, we are now getting many different errors (not from FieldSet). However, when I add to the dimensions: |
Beta Was this translation helpful? Give feedback.
-
|
If you want 2D simulations (so at the surface), you should not include dimensions = {
'U': {'lon': 'xi_rho', 'lat': 'eta_rho', 'time': 'ocean_time'},
'V': {'lon': 'xi_rho', 'lat': 'eta_rho', 'time': 'ocean_time'}
}Parcels will then assume that there is no depth dimensions, and particles will move horizontally using the first depth level |
Beta Was this translation helpful? Give feedback.
-
|
Just to jump in as a long time ROMS user. Zeta is NOT the depth, it is the free surface height, which can be negative! Also, note that ROMS grids, as you would expect for a naive C-grid implementation, do not have the same dimensions for any of the variables U, V, or Rho/T. Sketch out a c-grid and you can see why. It is actually quite odd that Nemo has the same size for all of its grids. A good picture to stare at can be found at |
Beta Was this translation helpful? Give feedback.
-
|
Hi @JamiePringle, thank you for all the insights on ROMS. First of all, thank you for pointing out on zeta. I'm not using it as I'm running a 2D simulation. This one is relevant also to @erikvansebille, the only reason I tried to add zeta is because without any depth dimension input argument, as Erik pointed out to me on his last comment: The error includes depth (FieldOutOfBoundError(p.lon, p.lat, p.depth) and out-of-bound at (x, y, 0.0). This is why I checked what happens if I add a depth dimension argument (there is no depth dimension in the file I'm using, only that zeta that has meter units and irrelevant as you said). And you are right, the dimensions of U are: |
Beta Was this translation helpful? Give feedback.
-
|
Alas, no, I have not tried to track particles in ROMS fields. I know Rob
Hetland and others have tried.
…On Wed, Jan 10, 2024 at 11:12 AM micgros ***@***.***> wrote:
CAUTION: This email originated from outside of the University System. Do
not click links or open attachments unless you recognize the sender and
know the content is safe.
CAUTION: This email originated from outside of the University System. Do
not click links or open attachments unless you recognize the sender and
know the content is safe.
Hi @JamiePringle <https://github.com/JamiePringle>, thank you for all the
insights on ROMS. First of all, thank you for pointing out on zeta. I'm not
using it as I'm running a 2D simulation. This one is relevant also to
@erikvansebille <https://github.com/erikvansebille>, the only reason I
tried to add zeta is because without any depth dimension input argument, as
Erik pointed out to me on his last comment: dimensions = {'lon':
'xi_rho', 'lat': 'eta_rho', 'time': 'ocean_time'}, I get an error:
File "/Users/michal/anaconda3/envs/parcels2/lib/python3.12/site-packages/parcels/kernel.py", line 585, in execute
raise FieldOutOfBoundError(p.lon, p.lat, p.depth)
parcels.tools.statuscodes.FieldOutOfBoundError: Field sampled out-of-bound, at (172.9972981266724, -45.99935258501933, 0.0)
The error includes depth (FieldOutOfBoundError(p.lon, p.lat, * p.depth*)
and out-of-bound at (x, y, *0.0*). This is why I checked what happens if
I add a depth dimension argument (there is no depth dimension in the file
I'm using, only that zeta that has meter units and irrelevant as you said).
And you are right, the dimensions of U are: 455 272 124 while V's are:456
271 124. But then I'm not so sure whether @erikvansebille
<https://github.com/erikvansebille>'s way to read this file, using the
indices=indices (see above), is correct? Any suggestion?
—
Reply to this email directly, view it on GitHub
<#1492 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADBZR2ZWQTLRBLNGNIXHODLYN24WVAVCNFSM6AAAAABBMSBHP6VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DAOBSGYZDC>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
@JamiePringle Thanks anyway :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @JamiePringle ! I'm working with @micgros on loading a ROMS file and using it with @hetland if we could get your help on this, we would sure appreciate it! |
Beta Was this translation helpful? Give feedback.
-
|
The most recent think I've done with Parcels is in this script It's not new, and only 2D surface flow, so you may have to make some changes to make it work the way you want. Hopefully not too many changes are required. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much! We'll give it a go. |
Beta Was this translation helpful? Give feedback.
-
|
@hetland It worked!! Thank you very much for sharing the script! Using |
Beta Was this translation helpful? Give feedback.
The most recent think I've done with Parcels is in this script
It's not new, and only 2D surface flow, so you may have to make some changes to make it work the way you want. Hopefully not too many changes are required.