You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently used this for a project and faced several issues/shortcomings of the repository that can be improved. Here are some of the things:
Ability to auto-populate task fields based on labels found in the dataset and removal of the restriction of the task argument to be one of the standard ones
Having a --no-cuda argument in run_entity as well to allow users to test code on a machine without CUDA without actually interfering with the code. This is already present in run_relations, but has been skipped in this file for some reason.
All of these lines can be put under the if args.do_train as these are relevant only to that section and the other args.do_eval section already loads the model again like so
I am thinking of creating an independent issue for each of these and start working on including some of these fixes/features in the near future as I've already made quite a few changes locally for my project. Just wanted to get your thoughts on these issues and if there is something that I am missing.
The text was updated successfully, but these errors were encountered:
Hi, thanks for using our code and raising these issues. All the fixes/optimizations look good to me! You may create individual pull requests for them.
One thing to note is that please make sure the modifications are compatible with the current code, because I do think it is easy for people to reproduce the results in the paper. (e.g., you may add an option for --task to enable automatically collecting labels, and still support --task ace05)
Hi,
I recently used this for a project and faced several issues/shortcomings of the repository that can be improved. Here are some of the things:
task
argument to be one of the standard ones--no-cuda
argument inrun_entity
as well to allow users to test code on a machine without CUDA without actually interfering with the code. This is already present inrun_relations
, but has been skipped in this file for some reason.--do_predict
, which has already been raised in How to run a pretrained model on unlabeled data? #30All of these lines can be put under the
if args.do_train
as these are relevant only to that section and the otherargs.do_eval
section already loads the model again like soI am thinking of creating an independent issue for each of these and start working on including some of these fixes/features in the near future as I've already made quite a few changes locally for my project. Just wanted to get your thoughts on these issues and if there is something that I am missing.
The text was updated successfully, but these errors were encountered: