Closed PhillipsOwen closed 2 days ago
I installed a hot fix to the UI data web service to force the default to be the latest "official hurricane" run.
this will have to be undone after the hurricane passes. A more permanent solution is needed here.
RL and I had a slack discussion yesterday and he would like to make another change to the default startup.
RL: "Is it possible to "default latest coampsforecast" on the apsviz-nopp.adcircprediction.org site? In the longer term we need to think through a strategy for doing this systematically"
He further postulated that perhaps the run properties could contain information on how the the UI will be defaulted on startup.
He proposes a discussion on this topic to discover more details and a development strategy.
After further discussion with @BrianOBlanton, it seems that the desired solution to this is to add an endpoint to the UserSettings API. This endpoint will allow the user to set an instance name, and that instance will become the default view on the UI. Another options discussed was adding the functionality to the UI. However, that would necessitate adding user accounts. This issue can be discussed further in the 10/22 UI meeting.
instance name implementation questions...
yes, there would need to be a separate endpoint for setting this, one for each production / aws site.
generally, yes, instance names are distinct
yes, it will
Generally, we try not to do this, but it's not impossible for one to be reused. Probably unlikely for tropicals, but more likely for synoptic / GFS
they are generally short, <30 char, but we can impose such a constraint when the model operators set up an instance.
i have a question related to the new default instance name implementation and the NOPP only default startup forcing ensemble name to be "coampsforecast". is this still needed with the default instance name is enforcement?
I think the default will always be coampsforecast for the NOPP side, since the coamps meteorology is part of the NOPP project. But the ability to override the default may still be useful for the NOPP aite.
--
Cheers,
[A black text on a white background Description automatically generated]
Brian O. Blanton, Ph.D. Director of Earth Data Sciences Oceanographer Renaissance Computing Institute University of North Carolina at Chapel Hill 100 Europa Drive Suite 540 Chapel Hill, NC, 27517
@.**@.> 919-445-9620 (O)
From: Phil Owen @.> Date: Thursday, October 24, 2024 at 10:19 AM To: RENCI/APSViz-UI-V3 @.> Cc: Blanton, Brian @.>, Mention @.> Subject: Re: [RENCI/APSViz-UI-V3] Default layers - Force "official" hurricane runs (Issue #288)
i have a question related to the new default instance name implementation and the NOPP only default startup forcing ensemble name to be "coampsforecast". is this still needed?
— Reply to this email directly, view it on GitHubhttps://github.com/RENCI/APSViz-UI-V3/issues/288#issuecomment-2435428124, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AARBQQ7Y2D77OYI7RJUD3HDZ5D6V7AVCNFSM6AAAAABPUOXB72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZVGQZDQMJSGQ. You are receiving this because you were mentioned.Message ID: @.***>
This is done
OP: Brian.
The ensemble simulations like "veer" are causing all sorts of problems since we don't have a hurricane track for the UI that reflects the modification to the storm. Can we prevent the veer* layers from showing up as the default view? Because of the order in which the ensembles are executed, they will almost always be the most recent for an NHC run.
We still want them available thru the usual layer selection process, but just not as the default.