Spaces:
Sleeping
Sleeping
Commit History
-
mid save - parento frontier method added
7b1cb02 -
mid save - multicolinearity test completed
9473071
-
mid save
966233a
-
commonality analysis added
8391739 -
mid save
0d69b8d -
mid save - coefficient table edited
da52d3e
-
ridge applied
326f30c
-
feature frontier charts fixed
3ae7e9c -
final refactoring confirmation
6099949 -
refactoring phase 03
ac517af -
refactoring phase 2
73e9bba -
refactoring phase 1
7d8883b -
refactoring phase 0
66db16d -
mid save - refactoring
0a83bc8
-
mid save
0b4e94b -
mid save
ac8217a -
mid save
ce30a31 -
file storage logic added
d78c89a
-
mid save
d17d853
-
mid save
56c7232
-
mid save
cc90a8b -
mid save - marginalized multi feature coefficients fixed
6544a5b -
mid save
b47dbe5 -
mid save
ba7bc38 -
mid save
1590e9c
-
mid save
4e16976 -
chart monotonicity applied without filtering
06795a3 -
chart monotonicty added
6c9874a -
chart fixed
f0af035 -
chart fix
fec484a -
mid save
757954c -
mid save - refactoring
f801d54 -
chart rendering calculation refactored
98d26d1 -
mid save
dda2c4a
-
mid save
d79a3ee
-
marginal cost chart added
e3438f2 -
mid save
2216e0a -
mid-save
7bd45e7 -
visualization + marignal cost calculation + data refresh logic
5e206f1
-
Assistant checkpoint: Adjust frontier logic to remove conflicting points
M8chaaAssistant generated file changes: - modules/cost_spec.py: Adjust frontier logic to remove conflicting points instead of skipping - modules/report_charts.py: Adjust frontier logic to remove conflicting points instead of skipping --- User prompt: oh wait, we should adjust the logic so that, when 1krw per unti increase doesn't get valid, we should not skip the higher spec ones. Instead we should adjust the already selected ones so that it would fit both monotonicity and 1 krw per unit increase rules. Replit-Commit-Author: Assistant Replit-Commit-Session-Id: 9604e04b-f4ce-4015-8e33-431536e2f05f098180d -
Assistant checkpoint: Fix frontier logic to skip invalid points instead of stopping
M8chaaAssistant generated file changes: - modules/cost_spec.py: Fix monotonic frontier logic to skip invalid points instead of stopping - modules/report_charts.py: Fix monotonic frontier logic in chart generation to skip invalid points --- User prompt: what the heck, the 1krw per feature value unit increase seems to mess up the whole calculation. some are skipping valid points and some are not connecting the data sample's last point. are you sure the calculation checks up 1krw/a feature value unit increase? It just need to skip and look for next point validation when (price diff)/(feature unit diff) isn't over 1.0 Replit-Commit-Author: Assistant Replit-Commit-Session-Id: 9604e04b-f4ce-4015-8e33-431536e2f05fcc32d89 -
Assistant checkpoint: Fix indentation error in cost_spec.py
M8chaaAssistant generated file changes: - modules/cost_spec.py: Fix indentation error on line 185 --- User prompt: fix this issue Replit-Commit-Author: Assistant Replit-Commit-Session-Id: 9604e04b-f4ce-4015-8e33-431536e2f05f17d803f -
Assistant checkpoint: Implement 1 KRW per feature unit cost increase rule
M8chaaAssistant generated file changes: - modules/cost_spec.py: Change to 1 KRW per feature value unit increase rule, Update endpoint condition for per-unit cost rule - modules/report_charts.py: Change to 1 KRW per feature value unit increase rule Change to 1 KRW per feature value unit increase rule Update monotonic increase rule for per-unit cost --- User prompt: yes Replit-Commit-Author: Assistant Replit-Commit-Session-Id: 9604e04b-f4ce-4015-8e33-431536e2f05f24abb26 -
Assistant checkpoint: Add tie-breaking logic for higher spec points at same cost
M8chaaAssistant generated file changes: - modules/report_charts.py: Add tie-breaking logic for same cost but different feature values - modules/cost_spec.py: Add tie-breaking logic for same cost but different feature values --- User prompt: uhh, you forgot to do this thing where if two points have the same price but one of them has more feature values, we consider it as higher spec so we should also choose the latter one. Replit-Commit-Author: Assistant Replit-Commit-Session-Id: 9604e04b-f4ce-4015-8e33-431536e2f05f71fe9a9 -
Assistant checkpoint: Updated frontier selection with replacement logic
M8chaaAssistant generated file changes: - modules/report_charts.py: Update frontier selection with replacement logic and proper (0,0) handling - modules/cost_spec.py: Update frontier creation with replacement logic and proper (0,0) handling --- User prompt: I need you to edit the code so that when selecting frontier points, the already selected points are not always finalized. If a latter points to be evaluated is more optimum than the previous one, it should replace. Actually if the points to be calculated is so strong and optimum that it changes all the previous points, it should do so 'until' it satisfy the monotonicity rule. For example, if point A B C in an increasing spec order have 1 krw 3 krw 5 krw, but then suddenly point D have 2 krw, then point B and C are eliminated. Point A isn't eliminated because it's fine. The point of 0 feature value should be a starting point unless: we don't have a point of 0 feature value it gets eliminated due to the next point, if those two happe…900f0a6
-
html error fix and refactoring
f1f99bf -
html error fix and refactoring
f698a9c -
html error fix
9df0fcc -
html error fix
2802c27 -
html error fix
56ce73b