Multiple sessions 2 #44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
… for concurrent sessions. Downloads into session-specific folders works, as does script monitoring and cancelling. Radar download status needs to be addressed, and all variables within RadarServer object need to be moved to dcc.Store in a dict.
…c.Store. Radar download and mungering dealt with. Monitoring broken for now.
…tep now. Munger and hodograph monitors inactive right now.
…ppear to be working.
…t application. Getting simulation/clock controls working again, but not quite there...issues with passing updated clock info/datetimes in manage_clock_ function.
…ed_dropdown nor change_time dropdowns update anything, but the rest of the logic seems to be working.
…e launch simulation button clicked, otherwise an error is thrown since one of the dicts hasn't been defined yet. Address playback speed or time selection dropdown restarting a paused simulation
… passing large dictionaries back and forth.
…f radar selections occasionally briefly showing as valid and then reverting.
…icable behavior when selecting radar sites (some would disappear immediately, others wouldn't even register). Set initial dynamic container which sets up app layout to only execute once with a new dcc.Interval. Only turn on monitor function when download and processing scripts are running.
…p to dynamically generate links based on session id.
…spose to a site. If they switched to 2 or 3 radars, the previous "shifted" radar would still be applied. 2) status updates wouldn't complete on hodos as scripts ended before a final pass of monitor() could be made. 3) configs dict from dcc.Store could be None on initial page load.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR with some design changes to allow concurrent sessions. Each session (which presently is each tab) is tagged with an id defined as the initial epoch millisecond. As long as a user keeps a tab open, it will reference the same id, but each new tab will initialize a new app instance.
Application is initialized from the config file, and then the layout is built out in generate_layout in
app.py. Global RadarSimulator object variables moved into two dictionaries (sim_timesandradar_info) which are stored indcc.Storeobjects which are stateless and preserve session independence. Some code configuration changes needed to reference thedcc.Storedata as this can only be done through callbacks. Output paths are passed directly to all scripts (Nexrad, munger, hodo, nse, etc.).Simulation data and output/placefiles are stored in
data/SESSION_IDandassets/SESSION_ID. Two logfiles indata/logsmonitor all sessions concurrently.This PR fixes #41. A browser-dependent bug in the handling of the
dcc.Storeobject which holds theradar_infodictionary was uncovered when accessing the app in Firefox: #43.