Reflection

[danfke]

rubric={reasoning:6}

In this section, your group should document what you have implemented in your dashboard so far and explain what is not yet implemented. It is important that you include what you know is not working in your dashboard, so that your TAs can distinguish between features in development and bugs.

This week it is suitable to include thoughts on the feedback you received from your peer and/or TA, e.g.

• Has it been easy to use your app?
• What differences are there between the DashR and DashPy app?
• Are there reoccurring themes in your feedback on what is good and what can be improved?
• Is there any feedback (or other insight) that you have found particularly valuable during your dashboard development?

This section should be around 300-500 words and the reflection-milestone4.md document should live in your GitHub.com repo in the doc folder.

[scarlqq]

• For What differences are there between the DashR and DashPy app? part

  We have tried to make the DashR and DashPy (Milestone 2 version, we updated DashPy app in milestone 4) apps look essentially identical in function as far as possible, and from the results it does. Only the color theme used in the map is different. We used plotly for our plots in R, so we also changed our layout from html.Iframe to dccGraph for the plots to have more interactive functions, i.e. zoom in and out.

• For what you have implemented in your dashboard so far and explain what is not yet implemented (Layout and deployment) part

  For dashPy, we did what we wanted in our sketch. However, it was a little bit difficult for us to center our stressor plot in the frame since we may have different widths with the different number of states users chose. We tried to use style={"width": "100%", "align":"center"}, put a html.Div out of the frame and use style, dcc.Loading, but seems none of them helped. We also found some problems with deployment of DashR. Although it works fine locally, the widgets and plots in the app are not visible sometimes after being deployed on Heroku. From the discussion in the group and on slack, it seems that our DashR app is not the only one suffering from this problem and we are still trying to work out how to fix it. We also had difficulty when trying to compose up docker in DashR. We can build the image successfully, but cannot open the app using 0.0.0.0:8050 (which should be localhost:8050 in local but gave us a message of "refuse the connection"). David tried to modify the port we are using in dockerfile and that finally solved the problem.