-
Notifications
You must be signed in to change notification settings - Fork 13
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
Search Term Quoting Issue in the Query Command #4
Comments
Hi @complexbrains, no bother at all, thank you very much for reporting this! |
Also I will add a check to stop more gracefully when the search returns no results. |
Thank you so much for the reply, really helps indeed. Actually I tried both in MacBook and Windows 10 and with the code in v 0.0.1 and the code in the main brunch, but in both cases, the double quote only works when the query contains term and date combinations. So no quoting only works if there is a single term, and double quoting only works with term + date but not with a single term or several terms to query. So not having a consistent pattern makes it really hard to guess what is the reason atm but I will be digging on it soon too! Surely I love the features in the main repo! Will make sure hackathon participants download that version too so we can build upon. I had one error with running the pipeline with the main branch, but I have to repeat it and then will report it too. Thank you so so much🤗 |
Thanks for this information; I still think this has to do with the shell's parsing of quotes and splitting of the command line rather than nqdc itself, but it would certainly help if you could provide the exact commands and corresponding errors. In any case writing the query in a file and using glad to hear you will use this in the (brainhack?) hackathon, is the project description online? I could push a release to PyPI before if you think it is necessary. let me know of any other problems you run into! |
Oh surely, it should be something to do with the shell indeed. I do not have access to the MacBook I tried currently but the command I tried and worked with windows 10 with version 0.0.1 is
I tried with the text file but gave me below error
writing the query word in the file either with single quote, double quote or no quote
somehow it cannot read the word I believe. At the moment I have a work around but will have a more intensive look after brainhack finishes. And indeed, finally we are ready to participate in OHBM Brainhack with NeuroCausal as Vale shared its details at our meeting. We will be using the data you provided but start with filtering it out to the clinical studies and move on from there. We are working on the pipeline I will share it with you once it is finalized so would be happy to hear your thoughts on that. Thank you so much again for your help, will update you on this issue for sure! |
thanks for trying it! could you share |
I just tried on windows command prompt and cannot reproduce the issue; if you are still experiencing this with the current |
after IRL discussion this seems to be resolved so closing |
Dear @jeromedockes
Sorry to bother you with this silly issue but I wondered do you think there might be a change with using the quote in the query with eutils somehow that might be giving me the error below? Since if I use the quotes with the query term as written in Readme as;
nqdc_full_pipeline ./nqdc_data -q 'fMRI[title]'
gives me zero downloads hence cannot move on with the further processes as in the below output:
however, it works fine if I query the term without the quotes.
Similarly
nqdc_download -q 'fMRI[Title] AND ("2019"[PubDate] : "2019"[PubDate])' nqdc_data
also seems like not working with the way it is constructed and gives the error below:nqdc_download: error: unrecognized arguments: (2019[PubDate] : 2019[PubDate])' nqdc_data
however, it works well if I change it to:
nqdc_download -q "fMRI[Title] AND (2019[PubDate] : 2019[PubDate])"
So tiny differences but I just wondered is there a workaround that I am missing somehow, which might be highly likely 🙄 or would it be due to a change eutils might have done with querying somehow?
If you think these need to be changed in the repo, given I know how busy you are, I would be more than happy to make the PRs as needed.
Thank you 🤗
The text was updated successfully, but these errors were encountered: