-
Notifications
You must be signed in to change notification settings - Fork 4
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
Test scores are printed twice (once with Logger, once alone) #54
Comments
Can't reproduce this. Could you tell me how you started the script? |
|
Mmhhh, sorry but I am not sure where this `pandora-train` is coming from...
have you an alias for it?
2017-10-04 10:09 GMT+02:00 Thibault Clérice <[email protected]>:
… pandora-train config_chrestien.txt --dev data/chrestien/dev --train
data/chrestien/train --test data/chrestien/test --eval_file
chrestiens_pos_logs_pytorch.csv
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF6HoyQmmYTDaqc3xwaiPepaUXMir1DPks5soz0zgaJpZM4Prqiu>
.
--
Enrique Manjavacas.
|
this naming stuff should be resolved through the uniformization of the cli
scripts?
…On Wed, Oct 4, 2017 at 10:14 AM, Enrique Manjavacas < ***@***.***> wrote:
Mmhhh, sorry but I am not sure where this `pandora-train` is coming from...
have you an alias for it?
2017-10-04 10:09 GMT+02:00 Thibault Clérice ***@***.***>:
> pandora-train config_chrestien.txt --dev data/chrestien/dev --train
> data/chrestien/train --test data/chrestien/test --eval_file
> chrestiens_pos_logs_pytorch.csv
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#54#
issuecomment-334080808>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AF6HoyQmmYTDaqc3xwaiPepaUXMir1DPks5soz0zgaJpZM4Prqiu>
> .
>
--
Enrique Manjavacas.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AELJL0mgsFgsqch6yrRSXV3-ug_Y6MsGks5soz5TgaJpZM4Prqiu>
.
|
This alias is just coming from here https://github.com/hipster-philology/pandora/blob/master/setup-gpu.py#L35-L40 which should be the default way to load in a cli (the methods, not the alias) |
Ok, thanks. I can't install setup-gpu.py because of this error |
it should not be an issue if you use the current main.py which uses the same exact client. It might lessen your pain with the setup file. I only use |
main.py throws
`Traceback (most recent call last):
File "main.py", line 6, in <module>
cli_train()
File "/home/manjavacas/code/python/pandora/pandora/cli.py", line 144, in
cli_train
train_func(**vars(parser.parse_args()))
File "/home/manjavacas/code/python/pandora/pandora/cli.py", line 94, in
train_func
tagger.setup_to_train(**data_sets)
File "/home/manjavacas/code/python/pandora/pandora/tagger.py", line 207,
in setup_to_train
min_lem_cnt=self.min_lem_cnt)
File "/home/manjavacas/code/python/pandora/pandora/preprocessing.py",
line 383, in fit
self.max_token_len = len(max(tokens, key=len)) + 1
ValueError: max() arg is an empty sequence
`
which is the reason why I was using train.py (now I remember). Note that I
don't have a test corpus...
2017-10-04 10:30 GMT+02:00 Thibault Clérice <[email protected]>:
… it should not be an issue if you use the current main.py which uses the
same exact client. It might lessen your pain with the setup file. python
main.py is the equivalent for now of pandora-train. Note that after #59
<#59> is merged, python
train.py will be the equivalent of pandora-train.
I only use python setup.py or setup-gpu.py develop in virtualenv
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF6Ho9JHxABH_xQRH8Ty9BQvYHaO3A4cks5so0I3gaJpZM4Prqiu>
.
--
Enrique Manjavacas.
|
Take a look at the two PR, that should solve those issues. |
Just a reminder that the issue at the bottom of #55 is still there (even after those two PRs). I'd like to continue debugging the predict time issue, but I am gonna need a fix for this first. |
I think I might have identified the source of your difficulties in #55 (see there). |
A fix for this one is incoming. |
The text was updated successfully, but these errors were encountered: