Added some more content and instructions

app.py

@@ -83,6 +83,18 @@ def parse_all_data(path):
 
 # Create the layout for the app
 app.layout = html.Div([
+    html.Div([
+        html.B("This is an interactive demonstration of case study results to showcase the ability of modeling and simulation to help envision distributed work systems"),
+        html.Br(),
+        dcc.Markdown("This interactive demo was performed under NASA contract number 80NSSC23CA121.",  id="explanation")
+    ], style={'width': '100%', 'border': '1px solid gray'}),
+    html.Div([
+        dcc.Markdown("It is envisioned that in future operatoins, each UAV is going to be controlled using a command and control (C2) link that allows communication with the remote pilot. This architecture can have potentially dangerous implications in the case of a failure of the command and control link. The UAV's are envisioned to be programmed with one or more contingency procedures that are to be executed in the case of a lost link. For example, to divert to and land at the nearest vertiport or continue along its preapproved route. This brings the question of how will the rest of the system need to react to the change in the aircraft trajectory. Is a system like this robust to an event like loss of link? ",  id="explanation2")
+    ], style={'width': '100%', 'border': '1px solid gray'}),
+    html.Div([
+        dcc.Markdown("If the dropdown menu is empty please wait a few seconds to allow the data to load. If the data doesnt load then click the submit button to force reload the dropdown. The files that contain data will take a few seconds to load so please be patient.",  id="explanation"),
+            html.Button('Submit', id='submit-button', n_clicks=0)
+    ], style={'width': '100%', 'border': '1px solid gray'}),
     html.Div([
 #        html.Div([
 #            html.Div("Select the desired input conditions, then click 'Simulate!':", id='text1'),
@@ -117,18 +129,6 @@ app.layout = html.Div([
 #            html.Br(),
 #            html.Button('Simulate!', id='button', n_clicks=0),
 #        ], style={'width': '50%', 'border': '1px solid gray'}),
-
-        html.Div([
-            html.B("This is an interactive demonstration of the What's Next Diagram for evaluating the ability of an operator to coordinate with envisioned automated systems, given a particular system design."),
-            html.Br(),
-            dcc.Markdown("More information can be found in the associated proceedings paper: Post, A., Nijveldt, R., Woods, D.D., IJtsma, M. (2024). Determining What's Next: Visual Analytics for Evaluating Human-Automation Coordination. Proceedings of the 2024 Human Factor and Ergonomics Annual Meeting, Phoenix, AZ. This work is partially funded by NSF Early Career Award #2238402 to Dr. Martijn IJtsma. This interactive demo also builds on earlier work under NASA grant 80NSSC23CA121.",  id="explanation")
-        ], style={'width': '100%', 'border': '1px solid gray'}),
-        html.Div([
-            dcc.Markdown("The example highlights a coordination problem in the operations of Unmanned Aerial Vehicle (UAV), which is the loss of a command and control (C2) link to the ground operator when the UAV *GCCRaven* is in busy airspace (i.e., there is surrounding traffic). The C2 link is used to receive data in real-time about the state/activity of GCCRaven, onboard automation, and to (re-)direct the automation to change GCCRaven's behavior. We use the What's Next Diagram to identify how the pilot of a second aircraft, *SNLBlaze* can coordinate with *GCCRaven*.",  id="explanation")
-        ], style={'width': '100%', 'border': '1px solid gray'}),
-        html.Div([
-            dcc.Markdown("It is envisioned that in future operatoins, each UAV is programmed with one or more contingency procedures that are to be executed in the case of a lost link. For this example, we assume the contingency procedure is to divert to and land at the nearest vertiport. However, even with contingency procedures onboard, there is potential for ambiguity in what GCCRaven will do next, depending on the logic that GCCRaven uses for determining what the nearest vertiport is, feedback it provides (Woods & Balkin, 2018), and--quite possibly--any related or additional failures onboard the UAV. The operator of *SNLBlaze* must therefore determine in real-time if what they think is the controlling contingency procedure is in fact being followed.",  id="explanation2")
-        ], style={'width': '100%', 'border': '1px solid gray'}),
         html.Div([
 #            html.Div("Next, input the relative path to your results folder, then click 'Submit'. This will load the data:", id='text2'),
 #            dcc.Input(
@@ -140,7 +140,7 @@ app.layout = html.Div([
 #            ),
 #            html.Button('Submit', id='submit-button', n_clicks=0),
             # Create a dropdown menu with the subfolders as options
-            html.Div("Once all subfolders are loaded (representing the different conditions you ran in WMC), you can select which one to plot:", id='text2'),
+            html.Div("Select which condition to load in the interactive graphs:", id='text2'),
             dcc.Dropdown(
                 id='subfolder-dropdown',
                 value=None #subfolders[0]  # Default value
@@ -225,16 +225,17 @@ def run_wmc(workAllocation, selected_time, ConAircraftResponse, OtherAircraftRes
 @app.callback(
     dash.dependencies.Output('subfolder-dropdown', 'options'),
     dash.dependencies.Output('variable-dropdown', 'options'),
-#    dash.dependencies.Output('submit-button', 'n_clicks'),  # Add this output to reset submit button clicks
-    [dash.dependencies.Input('interval-component', 'n_intervals')],
+    dash.dependencies.Output('submit-button', 'n_clicks'),  # Add this output to reset submit button clicks
+    [dash.dependencies.Input('interval-component', 'n_intervals'),
+     dash.dependencies.Input('submit-button', 'n_clicks')],
 #    [dash.dependencies.Input('path-input', 'value')],
 )
-def load_data(n_intervals):
+def load_data(n_intervals, n_clicks):
     selected_path = "Results"
     print("selected path is",selected_path)
     global data_store
 
-    if n_intervals > 0:
+    if n_intervals > 0 or n_clicks > 0:
         if selected_path is None or not os.path.isdir(selected_path):
             return [], []
         subfolder_labels, data = parse_all_data(selected_path)
@@ -244,9 +245,9 @@ def load_data(n_intervals):
         # Store data in the global dictionary
         data_store = data
         labels = list(data[list(data.keys())[0]]['aircraft_data'][list(data[list(data.keys())[0]]['aircraft_data'].keys())[0]].columns.tolist())  # Extracting column names for the first aircraft-specific dataframe
-        return subfolder_labels, labels
+        return subfolder_labels, labels, 0
     else:
-        return [], []
+        return [], [], 0
 
 # Define the callback to update the graphs based on the slider value
 @app.callback(