-
Notifications
You must be signed in to change notification settings - Fork 16
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
BUG/DOC: Tutorial eval and predict configs missing sections with model names #734
Comments
Hey @harshidapancholi sorry you're running into this issue. This is our fault 😳 [TweetyNet.optimizer]
lr = 0.001 Can you please try with the attached config and tell me if it works? My fault, thank you for catching this! I think it might also work if you literally just wrote [TweetyNet.optimizer] (with no key-value pairs underneath the table name) It's a limitation of the current config file format that we have to add a "dummy" table for the network even if we don't change any options, will make a note that we need to fix this |
A different error: (vak-env) C:\Users\RobertsLab\Desktop\vak-demo\gy6or6>vak eval gy6or6_eval.toml The above exception was the direct cause of the following exception: Traceback (most recent call last): |
Oh whoops, due to a typo because I accidentally typed an "s" at the end of the file 🤦 Try this one, please |
I deleted the s, and its running right now. It did throw up this message, not sure if I should just ignore it: (vak-env) C:\Users\RobertsLab\Desktop\vak-demo\gy6or6>vak eval gy6or6_eval.toml |
Great! I haven't seen that warning before. There's not much of a downside to lowering that option, like setting it to Are you working with zebra finch data? |
@NickleDave same error as before with the predict file.
ValueError: A config section specifies the model name 'TweetyNet', but there is no section named 'TweetyNet' in the config. |
Thank you @harshidapancholi for catching that. That config also needs a |
Fix/update options in doc/toml/gy6or6_train.toml Fix/update options in doc/toml/gy6or6_eval.toml Fix/update options in doc/toml/gy6or6_predict.toml
This should be fixed now, thanks @harshidapancholi |
Hi, I'm trying to run the vak tutorial and am running into an error during the evaluation step. I've double checked that I named all the directories as indicated, and here is the error I get.
(vak-env) C:\Users\RobertsLab\Desktop\vak-demo\gy6or6>vak eval gy6or6_eval.toml
2024-01-18 16:18:42,122 - vak.cli.eval - INFO - vak version: 1.0.0a3
2024-01-18 16:18:42,122 - vak.cli.eval - INFO - Logging results to C:\Users\RobertsLab\Desktop\vak-demo\gy6or6\results\eval
Traceback (most recent call last):
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\config\model.py", line 44, in config_from_toml_dict
model_config = toml_dict[model_name]
KeyError: 'TweetyNet'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\Scripts\vak-script.py", line 9, in
sys.exit(main())
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak_main_.py", line 48, in main
cli.cli(command=args.command, config_file=args.configfile)
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\cli\cli.py", line 54, in cli
COMMAND_FUNCTION_MAPcommand
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\cli\cli.py", line 4, in eval
eval(toml_path=toml_path)
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\cli\eval.py", line 41, in eval
model_config = config.model.config_from_toml_path(toml_path, model_name)
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\config\model.py", line 90, in config_from_toml_path
return config_from_toml_dict(config_dict, model_name)
File "C:\Users\RobertsLab\anaconda3\envs\vak-env\lib\site-packages\vak\config\model.py", line 46, in config_from_toml_dict
raise ValueError(
ValueError: A config section specifies the model name 'TweetyNet', but there is no section named 'TweetyNet' in the config.
Any help is appreciated, thank you!
The text was updated successfully, but these errors were encountered: