-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Experiments for Usability Evaluations #335
Comments
This seems low and incomplete to me. For instance, I would expect @dvenprasad can you determine if there might be an error on your end or upstream as part of this list #223 (comment) ? |
Okay, that was my bad. They were listed in E-GEOD-XXXX format. E-GEOD-10912 |
Is this updated list enough experiments for the evals? |
Yes, this will be enough for testing. |
@Miserlou @kurtwheeler @dongbohu These accessions should be part of the list of experiments we process first. |
Related: #54 |
@kurtwheeler will run in staging |
Context
For usability evaluations, I need to set up a scenario and have the user perform different tasks in the context of the scenario. @jaclyn-taroni suggested a scenario where the user will have to search for the term "imatinib"
Problem or idea
We need to ensure that the search term "imatinib" will return at least 6-10 results.
These are the accessions returned by GEO,ArrayExpress, and SRA for the search term 'imatinib' which is also part of the list in #223
E-MEXP-433
E-MTAB-2594
E-TABM-585
E-TABM-702
GSE22852
GSE30416
Solution or next step
We will need to keep a tab on these accessions and make a note whether they are processed or not.
Also, the number of experiments is on the lower end of what I would like. Would it be possible to explore an alternate scenario?
The text was updated successfully, but these errors were encountered: