-
Notifications
You must be signed in to change notification settings - Fork 6
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
Parametric wind runs #11
Comments
@mojy3995 I don't have anything to add. I ran a Florence case, I didn't really look at the results with nco tools, I just compared the station data qualitatively and it looked fine. |
Mojy hi,
I have run Florence using PaHM+ADCIRC and the results (water levels) look
ok (compared them
at different locations with co-ops observations).
Having said that, there were occasions where ADCIRC was producing high
water levels
but this was attributed to ADCIRC, the boundary conditions and at some
locations due to the bathymetry.
First step to suggest is: run PaHM in stand-alone mode, produce the
atmospheric fields and compare
them with observations to see if the comparisons make sense.
If the results are ok, the focus then will be SCHISM and/or bathymetry.
By the way, have you plotted out the wind fields coming out from SCHISM?
Takis
Panagiotis Velissariou, Ph.D., P.E.
UCAR Scientist
National Ocean and Atmospheric Administration
National Ocean Service
Office of Coast Survey CSDL/CMMB
Project Lead - Coastal Coupling
cell: (205) 227-9141
email: ***@***.***
…On Thu, Sep 15, 2022 at 1:42 PM Mojy ***@***.***> wrote:
@saeed-moghimi-noaa <https://github.com/saeed-moghimi-noaa>
@SorooshMani-NOAA <https://github.com/SorooshMani-NOAA> @pvelissariou1
<https://github.com/pvelissariou1>
Here is the list of runs that Soroosh and I did with Sergey wind track and
the Florence one:
Mojy:
Sergey wind track: wrong elevation results
Florence wind track: Package from Soroosh: Min elev=-707, Max elev=
1124.797
Florence wind track: re-create the track by using python code: Min
elev=-59, Max elev=3
Soroosh:
Sergey wind track- wrong elevation results
Before sending a note to Sergey to compare the wind track file with the
Florence track file, I just wanted to make sure that there is nothing wrong
with our process, particularly, the python code process.
Soroosh could you please add any run that you did here?
Any thought Saeed & Takis? I think this is a great opportunity to test all
process with another track.
—
Reply to this email directly, view it on GitHub
<#11>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/APC7TPZF23UVOZMSZC6WCRLV6NUZXANCNFSM6AAAAAAQNVEK64>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Hi Takis, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@saeed-moghimi-noaa @SorooshMani-NOAA @pvelissariou1
Here is the list of runs that Soroosh and I did with Sergey wind track and the Florence one:
Mojy:
Sergey wind track: wrong elevation results
Florence wind track: Package from Soroosh: Min elev=-707, Max elev= 1124.797
Florence wind track: re-create the track by using python code: Min elev=-59, Max elev=3
Soroosh:
Sergey wind track- wrong elevation results
Before sending a note to Sergey to compare the wind track file with the Florence track file, I just wanted to make sure that there is nothing wrong with our process, particularly, the python code process.
Soroosh could you please add any run that you did here?
Any thought Saeed & Takis? I think this is a great opportunity to test all process with another track.
The text was updated successfully, but these errors were encountered: