Comments (5)
When a trial is stopped by a scheduler such as ASHA, a stopping signal is sent to the trial.
If some metrics are emitted before this signal is seen, those metrics are not communicated to the scheduler and not shown in summary table (however, they are taken into account when showing the best trial at the end).
The reason for not showing this result to schedulers is that most of them would not support acting on results seen after they emit a stopping decision.
from syne-tune.
One thing we could do is to report results in this table even after stopping decisions even though scheduler would not see those results.
from syne-tune.
Thanks for your explanation! I think in some cases it could help to report. For example in my case just some profiling printouts failed at the end of training for a few trials, but only after diving deeper into it did I realize that those ones actually performed the best.
from syne-tune.
Hello @austinmw , can we close this issue? I think that whenever a trial script fails, Syne Tune will not consider future results coming from there, this is probably a safe behaviour, right?
from syne-tune.
Sure, that makes sense to me, thanks.
from syne-tune.
Related Issues (20)
- Allow for list-valued hyperparameters HOT 6
- Yahpo blackbox not matching direct calls to yahpo
- Grid Search creates more trials than candidates HOT 2
- Track train/validation metrics in the Sagemaker dashboard when doing remote tuning HOT 11
- Control SyneTune logging verbosity HOT 2
- Change default output folder for model checkpointing. HOT 3
- RTD Search broken + Question Regarding Status HOT 11
- Wrong Usage of np.random.randint HOT 1
- follow-up: make sure customers can easily run example scripts HOT 1
- Reduce the number of manual steps required for each release
- Flexibility in the number of GPUs when using LocalBackend HOT 2
- Questions on benchmarking HOT 5
- Run launch_lcbench_simulated.py, get ValueError exception HOT 7
- Unreproducible Results given seed HOT 9
- MORE fails with uniform configuration space HOT 1
- Slow Execution of MOBSTER Algorithm for Tabulated Benchmarks HOT 4
- examples/launch_asha_yahpo.py not working HOT 2
- examples/launch_height_sagemaker_remotely.py does not work if distribute_trials_on_sagemaker = True HOT 1
- Unit tests in test_remote_launcher_path are commented out HOT 3
- RemoteLauncher corrupts requirements.txt when not ending with newline HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from syne-tune.