aathish04 / medict Goto Github PK

The user should be able to export the CSV or the contents of the Database into MS Excel file format.

Currently, list type field entries such as SYMPTOMS and TIMES are stored in the database in the format:

'["a","b","c"]'

It would be much better if these were changed to just strings:

"a,b,c"

By doing this, the parsing of the database entries at runtime is made much easier as a simple str.split() method can be called, instead of stripping the square brackets and making things unnecessarily complicated.

@naveen521kk

We need to make major changes to how imports work.

Currently, with folders arranged like they are, with one folder for each separate feature of manim, it is extremely unclean to import between packages.

For example, if I needed to use some method defined in one of your packages while inside my own package, I will be unable to do so.
I cannot do:

# I am in medict/csvmanager/csvwriter.py
from ..sqlmanager import SQLManager

The above code will NOT work.

Likewise, if you needed to import some CSV functionality (you have implemented this separately, which is not encouraged) from my scripts, you will be unable to do so.

THE MOST IMPORTANT REASON WHY OUR CURRENT SYSTEM IS TERRIBLE:

When we work on the Machine learning systems, we can neither use the SQL methods and code that you wrote, nor can we use the CSV manager methods that I wrote. It's absolutely horrible.

This is because we keep each separate script having the different functionality, in different folders.

When a module is imported, it is unable to go out of its current folder and import from it's parent directory because the __init__.py file is right next to it and it thinks it's in the highest directory possible.

There is a way to allow for such imports without changing the directory structure. However it is a very dangerous and bad method.

You can sys.path.append("/full/path/to/module/") but that is EXTREMELY bad practice.

For this reason, I suggest that we can make a single folder named features inside of which we can keep all the different files csvwriter.py, sqlmanager.py etc. This will allow easily importing between each other and would allow us to ACTUALLY work on ML.

In these lines age is stored as STR. Change it to Number. I found it difficult while converting to MySql.

We need to put the SQL Viewing table into it's own tab in the main window defined at medict.py.

This can be done much easier after #21 is finished.

If the user wishes, they can see the X-RAY/ CT scans of the selected patient.

For the sake of code cleanliness, it is better to have a single module handling all of the CSV related issues. sqlmain.py should not have any csv related code at all.

The function defined at:

Is the same as the function defined at:

There is absolutely no need to repeat code again and again.

I plan to implement a small config file which the user can set it up, which will contain the details of the Mysql server and database. What else should be there in that config file? @Aathish04
Btw it will use https://docs.python.org/3/library/configparser.html

If the user wishes, they can push the CSV to an FTP server, supplying the proper credentials and stuff.

• Can be COVID-19 (Preferred)
• Can be any disease etc.

The current dataset is the reports available at sirm.org.

They are detailed enough for us to use, but they do not state any information about the mortality of the patients, and I assume they all lived.

Any thoughts?

Let the user see the differences between the local CSV and the database (what fields have been changed etc).

Allow the user to merge from one data source to the other.

On opening a Python Shell in the medict directory and running import sqlparser, an error is thrown, and has been pasted below.

Python 3.7.7 (default, Mar 10 2020, 15:43:33) 
[Clang 11.0.0 (clang-1100.0.33.17)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sqlparser
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/Users/aathishs/Python/MedictEnv/medict/sqlparser/__init__.py", line 2, in <module>
    import main
ModuleNotFoundError: No module named 'main'

@naveen521kk I don't know how exactly you plan on allowing us to use the sql parser. Is this the correct way, or is this an actual bug?

Remove this line just because who wants to delete all the database?

We need to put the SQL Viewing table into it's own tab in the main window defined at medict.py.

This can be done much easier after #21 is finished.

This is an issue to remove all the Debug statements like print for the code which is an absolute waste with no use to the user as well as to us.

When the user enters a particular parameter, a graph/plot should be displayed that visualises all the data with respect to that parameter.

I think we need to add an S.No column in CSV file as it would be quite helpful while checking between SQL and CSV. What do you think @Aathish04

Allow for easily changing the font size if the user needs it.

Write a function to modify a single row of a database.

What can we use to make a UI? There are many options available. I prefer using something like HTML and JS and CSS for UI. But using Tkinter is also ok for me, so we should select wisely so that it doesn't become a big problem for us later on. What is your opinion about it @Aathish04 .

Allow the user to hear what the mouse is hovering over, if kept for over 2 seconds.

Allow the user to switch between multiple colour themes.

Many/All of the functions defined in sqlmain.py can be made into methods of SQLManager.

Once that is done, SQLManager can be imported, and will be the single place from which all SQL related methods, functions and objects can be taken.

Essentially, move all the functions and variables in sqlmain.py and convert them into methods and attributes of SQLManager.

We want a good font for using in UI rather than default one. It should also look good. This issue deals what font to select.
We can get fonts from https://fonts.google.com or any font with commercial use.