-
Notifications
You must be signed in to change notification settings - Fork 3
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
Dots and dashes in model names #82
Comments
Hi Damien, did you use the latest clef? |
@paolap Yep, I used version 0.5.0. |
Hi Damien I can't reproduce your issue, what occurs to me is that maybe you're using directly the 'local_query' function rather than 'search' which calls other functions before to check the arguments and values you're passing and fixes them if they need to. We've also updated the read the docs now so there shouldn't be confusion anymore. |
No problem. Following this example I did the following:
|
It's weird for some reason the master branch we used had a faulty version you can see here: if 'model' in args.keys(): should be if 'model' in args.keys(): we're calling the function but we don't update the value. This have been deleted accidentally at some stage in one of the branches we merged, because my version still has the right syntax and no change has been done on this for a while. Thanks for getting back to me, somehow we were already using a fixed version. |
Thanks, @paolap |
This is now solved in localfix, I also noticed alternative model names weren't working for --remote option, they now work for everything. |
This is a very minor comment, but I've noticed that at the command line clef works fine with either dashes or dots between the numbers in model names, e.g.
CSIRO-Mk3.6.0
CSIRO-Mk3-6-0
whereas when using
import clef.code
within a script it only accepts dots.It probably wouldn't really matter except that the official model ids use dashes, so your first instinct as a user is to use
CSIRO-Mk3-6-0
.The text was updated successfully, but these errors were encountered: