-
Notifications
You must be signed in to change notification settings - Fork 10
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
ami-dictionaries
directory option not working as expected
#12
Comments
Thanks you.
I have modified the code and believe that the new release (today) will
solve this.Let's keep the issue open untill it has been verified
…On Fri, Feb 8, 2019 at 4:54 PM amit yadav ***@***.***> wrote:
Assigned #12 <#12> to @petermr
<https://github.com/petermr>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#12 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAsxSwaJAO0TDD2rFu6FzFI1FxBfsk5eks5vLau2gaJpZM4awkDu>
.
--
Peter Murray-Rust
Founder ContentMine.org
and
Reader Emeritus in Molecular Informatics
Dept. Of Chemistry, University of Cambridge, CB2 1EW, UK
|
Please retest and verify correction. |
This is tested on the latest release i.e
I am attaching a test script for the same. I hope it helps. Please change the file extension to |
Thanks!
On Sun, Feb 17, 2019 at 1:31 PM amit yadav ***@***.***> wrote:
This is tested on the latest release i.e ami20190216b
The above issue is partially resolved.
The dictionary files are correctly created in the specified directory
option, but the two not so required directories are still created:
- Contentmine under the home directory
Will think about this.
- target in the current working directory (this is not created for
dictionary creation from terms)
Yes - I think this is a feature that should be removed.
I am attaching a test script for the same. I hope it helps. Please change
the file extension to .sh,
Don't understand this. I can commit *.sh files. What's the error message?
Github didn't allow me to upload file with that extension.
test_issue_12.txt
<https://github.com/petermr/tigr2ess/files/2872980/test_issue_12.txt>
I'll look at this and commit it myself
—
… You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAsxS2BI9xEpVgyS99xeDK2sQn9ACnJAks5vOVnEgaJpZM4awkDu>
.
--
Peter Murray-Rust
Founder ContentMine.org
and
Reader Emeritus in Molecular Informatics
Dept. Of Chemistry, University of Cambridge, CB2 1EW, UK
|
I have added this and edited:
* don't include hard-coded directories (e.g. /home/amit) but use symbolic
variables. Then anyone can us them.
PLEASE TEST IT.
On Sun, Feb 17, 2019 at 7:55 PM Peter Murray-Rust <
[email protected]> wrote:
… Thanks!
On Sun, Feb 17, 2019 at 1:31 PM amit yadav ***@***.***>
wrote:
> This is tested on the latest release i.e ami20190216b
> The above issue is partially resolved.
> The dictionary files are correctly created in the specified directory
> option, but the two not so required directories are still created:
>
> - Contentmine under the home directory
>
> Will think about this.
>
> - target in the current working directory (this is not created for
> dictionary creation from terms)
>
> Yes - I think this is a feature that should be removed.
>
>
> I am attaching a test script for the same. I hope it helps. Please change
> the file extension to .sh,
>
Don't understand this. I can commit *.sh files. What's the error message?
> Github didn't allow me to upload file with that extension.
> test_issue_12.txt
> <https://github.com/petermr/tigr2ess/files/2872980/test_issue_12.txt>
>
I'll look at this and commit it myself
—
> You are receiving this because you modified the open/close state.
> Reply to this email directly, view it on GitHub
> <#12 (comment)>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAsxS2BI9xEpVgyS99xeDK2sQn9ACnJAks5vOVnEgaJpZM4awkDu>
> .
>
--
Peter Murray-Rust
Founder ContentMine.org
and
Reader Emeritus in Molecular Informatics
Dept. Of Chemistry, University of Cambridge, CB2 1EW, UK
--
Peter Murray-Rust
Founder ContentMine.org
and
Reader Emeritus in Molecular Informatics
Dept. Of Chemistry, University of Cambridge, CB2 1EW, UK
|
I tested the script amit_test.sh on the latest release i.e |
Operating system: Ubuntu 16.04
To create dictionary from wikipedia page of millet, as described at https://github.com/ContentMine/dictionaries/blob/master/MAKING.md, the following command is issued.
I was hoping to get the dictionary files at the path specified by
--directory
option above. Instead, the concerned dictionary files were created as per the below directory structure under/home/amit/
.And the following (apparently not required for the concerned purpose) directory structure was created in the current working directory.
The above behaviour was also observed for all the four different dictionary creation examples present in https://github.com/ContentMine/dictionaries/blob/master/MAKING.md.
The text was updated successfully, but these errors were encountered: