Closed MatteoWohlrapp closed 1 week ago
model JiGen is still missing?
Trainers like mldg dial also have gamma, that can be done also with id?
From what I can see, jigen has not hyper_init and hyper_update functions, so I assumed hyperparameters are not updated.
To the other question: In your initial issue, you split it into two parts. The first part, the gamma collision when combining trainers, is not addressed with this. The second part, where the naming of model parameters collides, is. Will need to think about the first part, as this won't work with ids
From what I can see, jigen has not hyper_init and hyper_update functions, so I assumed hyperparameters are not updated.
To the other question: In your initial issue, you split it into two parts. The first part, the gamma collision when combining trainers, is not addressed with this. The second part, where the naming of model parameters collides, is. Will need to think about the first part, as this won't work with ids
you are right, i forgt, sorry, jigen is a subclass of dann
I read the pr several times since it first launched, the key point i want to make sure is that this design will be consistent with extensions, for example, if we have hyperscheduler_dial_mldg trainer, training diva_hduva model.
Solved gamma_reg naming collision by introducing functionality to pass different gamma values for different trainers and models based on the naming of the class. With this comes a slight change in how the command line or yaml arguments are passed, however, the previous format is still supported. Also added parameter printing for models and trainers.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 95.23%. Comparing base (
faf7589
) to head (0d62919
).:exclamation: Current head 0d62919 differs from pull request most recent head bdf84c2
Please upload reports for the commit bdf84c2 to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@MatteoWohlrapp , could you fix the yaml according to my review?
Can't see a review
see the screenshot, the same scene not on your side?
@MatteoWohlrapp, the test coverage must be above 95%
currently
Attention: Patch coverage is 88.05970% with 8 lines in your changes are missing coverage. Please review.
Codecov Report
Attention: Patch coverage is
88.05970%
with8 lines
in your changes are missing coverage. Please review.Project coverage is 95.00%. Comparing base (
af8a238
) to head (cc650ad
). Report is 4 commits behind head on master.Files Patch % Lines domainlab/models/a_model.py 78.57% 3 Missing ⚠️ domainlab/algos/trainers/a_trainer.py 33.33% 2 Missing ⚠️ domainlab/arg_parser.py 83.33% 2 Missing ⚠️ domainlab/utils/hyperparameter_retrieval.py 88.88% 1 Missing ⚠️ Additional details and impacted files ☔ View full report in Codecov by Sentry. 📢 Have feedback on the report? Share it here.
@MatteoWohlrapp see detailed coverage report in quotes.
@MatteoWohlrapp , what is the test coverage at the moment?
One way to find this is run the pytest locally on a GPU node, or even better, change the CI yaml to display the coverage each time
You can also check it on the Codacity website here or refer to the screenshot below; it seems like it is fine now:
@MatteoWohlrapp
@MatteoWohlrapp
Run poetry run python examples/api/jigen_dann_transformer.py
Traceback (most recent call last):
File "/home/runner/work/DomainLab/DomainLab/examples/api/jigen_dann_transformer.py", line 9, in <module>
from domainlab.mk_exp import mk_exp
File "/home/runner/work/DomainLab/DomainLab/domainlab/mk_exp.py", line 4, in <module>
from domainlab.arg_parser import mk_parser_main
File "/home/runner/work/DomainLab/DomainLab/domainlab/arg_parser.py", line 33
my_dict = {} if "=" in values:
^
SyntaxError: invalid syntax
Error: Process completed with exit code 1.
@MatteoWohlrapp
Run poetry run python examples/api/jigen_dann_transformer.py Traceback (most recent call last): File "/home/runner/work/DomainLab/DomainLab/examples/api/jigen_dann_transformer.py", line 9, in <module> from domainlab.mk_exp import mk_exp File "/home/runner/work/DomainLab/DomainLab/domainlab/mk_exp.py", line 4, in <module> from domainlab.arg_parser import mk_parser_main File "/home/runner/work/DomainLab/DomainLab/domainlab/arg_parser.py", line 33 my_dict = {} if "=" in values: ^ SyntaxError: invalid syntax Error: Process completed with exit code 1.
lookes like error introduced by my commit
@MatteoWohlrapp
Run poetry run python examples/api/jigen_dann_transformer.py Traceback (most recent call last): File "/home/runner/work/DomainLab/DomainLab/examples/api/jigen_dann_transformer.py", line 9, in <module> from domainlab.mk_exp import mk_exp File "/home/runner/work/DomainLab/DomainLab/domainlab/mk_exp.py", line 4, in <module> from domainlab.arg_parser import mk_parser_main File "/home/runner/work/DomainLab/DomainLab/domainlab/arg_parser.py", line 33 my_dict = {} if "=" in values: ^ SyntaxError: invalid syntax Error: Process completed with exit code 1.
lookes like error introduced by my commit
you corrected that already in the last two commits.
Introduced a unique id for every object, which is added to the parameter name.