-
Notifications
You must be signed in to change notification settings - Fork 17
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
Create FAQ for the resource #62
Comments
Clarify why some perturbations have many replicates https://github.com/jump-cellpainting/megamap/issues/8 |
Clarify that for some plates, we have images but not anything else downstream. These plates failed QC but we kept them because they may be useful for developing QC methods. Also clarify that the load_data files are the right way to index into the dataset |
@afermg this is the FAQ issue I mentioned during checkin |
@shntnu Is the goal to translate these into an actual FAQ or just to link them? |
Translate them to an actual FAQ in the JUMP handbook, then close out this issue because we should track it in that repo instead (via PR's each time there is a new Q). What do you think? |
Sounds good to me
…On Fri, Mar 29, 2024 at 9:40 AM Shantanu Singh ***@***.***> wrote:
@shntnu <https://github.com/shntnu> Is the goal to translate these into
an actual FAQ or just to link them?
Translate them to an actual FAQ in the JUMP handbook, then close out this
issue because we should track it in that repo instead (via PR's each time
there is a new Q). What do you think?
—
Reply to this email directly, view it on GitHub
<#62 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADNQL2BVAY5PELFDQZ2EOL3Y2VVOPAVCNFSM6AAAAAAWVNFGZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRXGI3DGNZZGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think this is solved by broad.io/jump. I'll close this issue but LMK if there is anything else to be done. |
The FAQ itself is currently at this location |
I'll start this thread for collating FAQs. To get started, let's link out to issues that seem like good additions to the FAQ-to-be
The text was updated successfully, but these errors were encountered: