Closed nils-schmitt closed 5 months ago
Buttons should have a universal case convention.
module_metrics_analyzer.__rate_timestamp_correctness should use the liear_prob directly from the query_gpt() function
module_metrics_analyzer.__rate_timestamp_correctness should use the liear_prob directly from the query_gpt() function
I've refactored this already on my branch 👍 New code now looks like this.
timestamp_correctness, linear_probability = u.query_gpt(messages, return_linear_probability=True, top_logprobs=1)
and I changed the return value of the function accordingly.
This basically means having a final database image.
Remove all print statements
Fix ResultViewTests
add valid cohorts for all traces remaining in the db
In settings.py
there are these two lines that should be addressed:
# SECURITY WARNING: keep the secret key used in production secret!
SECRET_KEY = "django-insecure-$u00r=^xd*m1ggjgzwj%2o2$h=34k358#imaxe22w@stk_aptt"
# SECURITY WARNING: don't run with debug turned on in production!
DEBUG = True
Remove migrations directory from trace:comparator. It is empty aside from an init file so it should not be required. Especially because all models are located in the extraction app.
Push web scraping poc, with big future use annotation
Fix ResultViewTests
How thou???
Fix ResultViewTests
How thou???
Delete
Clean TTE html files
Make html files similar regarding Capitalization of words
Line 76 in module_activity_labler.py: user_message: List[str] = patient_journey_numbered
has wrong typing, should be str
.
The functions inside post_processing
in module_time_extractor.py use a variable df
that shadows a variable from outer scope. It should be changed to _df
inside those functions. Additionally the column
parameter is typed as a pd.Series
, but is actually a str
Here we should collect all the things, we see in the code check that are most certainly in the end product, but not desired. Feel free to contribute!
Database:
Code:
Optional: