Feature/diagnostics list

[brandonzhu09]

Description

Extended the application to display a list of diagnostics at a time given the attributes selected or not selected in the dropdown menu to constrain or broaden the diagnostics search. Separated the channel field to its own dropdown where its options are dynamically tied with the variable attribute. Also, rewrote unit tests for the Django API views, mainly the update_variable_option endpoint that was changed to accept new parameters (variable_name and channel).

Additional features:

• Created Dockerfile and docker-compose configuration files to setup and run the evagram application with multi-container services, including the frontend, backend, and the Postgres database. Updated the Readme to provide instructions to run Evagram on Docker.

Issues addressed

#20

[tariqhamzeyssai]

@brandonzhu09 Is this ready for review?

[brandonzhu09]

@brandonzhu09 Is this ready for review?

Yes, its ready!

[asewnath]

I don't know if you're also running into this problem, but if I run evagram_input (setting owner name to postgres and experiment name to a random name) I'm able to add plots to the database, but I don't see a new username in the dropdown menu

[brandonzhu09]

I don't know if you're also running into this problem, but if I run evagram_input (setting owner name to postgres and experiment name to a random name) I'm able to add plots to the database, but I don't see a new username in the dropdown menu

Shouldn't that be the intended behavior? If we are adding new experiments under the same owner, it shouldn't create a new username in the dropdown menu.

[asewnath]

I don't know if you're also running into this problem, but if I run evagram_input (setting owner name to postgres and experiment name to a random name) I'm able to add plots to the database, but I don't see a new username in the dropdown menu

Shouldn't that be the intended behavior? If we are adding new experiments under the same owner, it shouldn't create a new username in the dropdown menu.

To clarify, when I run evagram_input with a new username, I see that new username in the database but it doesn't appear in evagram's dropdown menus. I'm wondering if you're also encountering this problem or if it's an issue on my end

[brandonzhu09]

I just want to say here that I want to move forward with the bugfix for the cascading logic after this PR is merged into develop. I was working on the develop branch for the bugfix when I realized there were so many changes to the frontend logic that I would need to practically redo the bugfix with the new frontend in this PR. Let me know on your thoughts on how I should approach this!

[brandonzhu09]

I don't know if you're also running into this problem, but if I run evagram_input (setting owner name to postgres and experiment name to a random name) I'm able to add plots to the database, but I don't see a new username in the dropdown menu

Shouldn't that be the intended behavior? If we are adding new experiments under the same owner, it shouldn't create a new username in the dropdown menu.

To clarify, when I run evagram_input with a new username, I see that new username in the database but it doesn't appear in evagram's dropdown menus. I'm wondering if you're also encountering this problem or if it's an issue on my end

@asewnath I was able to recreate the problem you mentioned and found how to resolve it. What you have to do is to stop the postgresql service running on the host machine, run docker compose, and then use evagram_input to input data on the postgresql service running on the docker container. Hope this helps!

[tariqhamzeyssai]

I have not personally tested this, but we can move forward and revisit any remaining issues that may spring up. Thanks @brandonzhu09 for heeding our comments. Great work!