-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #1278, round 2: [Sim] Reframe to classify 'will price go up *anytime* in next 5 min?' #1281
base: main
Are you sure you want to change the base?
Conversation
…ytime* in next 5 min?', etc
…cit. Especially, change from labels of high/low to UP/DOWN, to make things explicit. I think I fixed a bug or two
Some benchmarks. Right after commit e475ee2, where I cleaned up separation of HIGH and LOW classifier models. Performance plots look a bit more sane.
Settings: my_ppss.yaml.txt
Plots to ignore: pdr/tdr profit vs prob_up, when prob_up < 0.5. (So far it's only plotting probs_up_UP)
|
Some benchmarks. Right after commit a03244e
Settings: same ppss as before: my_ppss.yaml.txt
|
…n't run tests yet. Lots to go.
…/pdr-backend into issue1278-reframe2
…to revising binmodel_data_factory heavily. Also: found a bug in _slice(), so wrote tests to btter characterize _slice(), and fixed the bug.
New experiments, with longer runsFour different experiments
Where
Parameters that are static across runs
Experiment 1: "reframe2" x "easy"All params: my_ppss.yaml.txt Final log line: Experiment 2: "reframe2" x "real"All params: my_ppss.yaml.txt Final log line: Experiment 3: "reframe3" x "easy"All params: Final log line: Experiment 4: "reframe3" x "real"All params: Final log line: Analysis / Discussion
|
Fixes #1278