Skip to content
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

added todo comments for clarification #15

Merged
merged 9 commits into from
Mar 11, 2024
Merged

added todo comments for clarification #15

merged 9 commits into from
Mar 11, 2024

Conversation

danieljgroso
Copy link
Contributor

@danieljgroso danieljgroso commented Feb 12, 2024

Description

Changes are non-functional in nature and include TODO comments. These comments are primarily serving to clarify some of the comments and descriptions of the code functionality and metadata.

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

N/A

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

@danieljgroso danieljgroso self-assigned this Feb 12, 2024
@danieljgroso
Copy link
Contributor Author

@cansavvy this should be ready to review! Please let me know if this style of review works for you or if you'd like to see something different

Copy link
Collaborator

@cansavvy cansavvy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@danieljgroso Thanks for these comments! This works quite nicely! Do you think you could take a whack at describing the things mentioned in the review?

This is where if you can dump any knowledge you have about these kinds of datasets we can help you craft it so it is helpful in this vignette when people are trying to learn this analysis!

vignettes/getting-started.Rmd Outdated Show resolved Hide resolved
vignettes/getting-started.Rmd Outdated Show resolved Hide resolved
vignettes/getting-started.Rmd Outdated Show resolved Hide resolved
vignettes/getting-started.Rmd Outdated Show resolved Hide resolved
example data caller (comment)
Copy link
Collaborator

@cansavvy cansavvy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Couple comments but thanks for these additions @danieljgroso ! I think we're close!

vignettes/getting-started.Rmd Outdated Show resolved Hide resolved
vignettes/getting-started.Rmd Show resolved Hide resolved
```{r}
library(magrittr)
library(gimap)
```

## Data requirements

TODO: What kind of data would someone need to run this? How much flexibility is there in what the experimental set up might look like?
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sobrien29 this might be a good question to address with Alice and the broader team; e.g. how many timepoints are required for minimum functionality, will we require the pgPEN library, etc

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I generally agree with the idea let's develop this for the Berger lab first and then we can try to expand this package's flexibility as we move along. But totally, this is probably a bigger and ongoing discussion amongst the team!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At minimum we need a T0 (or plasmid) and a later timepoint (actual timing is dependent mainly on cell growth kinetics). Intermediate timepoints can be included for a time-based analysis if wanted and I believe the test data includes one intermediate timepoint.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sobrien29 How would you describe this to a user in this context? What is a T0? That means just the first time point at 0 days? Do you have a paper we can link to that give people the basics of CRISPR screens?

@cansavvy cansavvy self-requested a review March 4, 2024 18:22
cansavvy and others added 2 commits March 4, 2024 13:45
Co-authored-by: Daniel J. Groso <95438884+danieljgroso@users.noreply.github.com>
Copy link
Collaborator

@cansavvy cansavvy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Just a few more things to wrap this up @danieljgroso and @sobrien29

  1. Delete all the TODOs (assuming they've been properly addressed) -- @cansavvy and @danieljgroso addressed this in 12ef572
  2. Can you add resources and links that would be helpful for context here?
  3. Can you address added todo comments for clarification #15 (comment) by adding information in the vignette?

Thanks! We're close!

@danieljgroso
Copy link
Contributor Author

This is great! Just a few more things to wrap this up @danieljgroso and @sobrien29

  1. Delete all the TODOs (assuming they've been properly addressed) -- @cansavvy and @danieljgroso addressed this in 12ef572
  2. Can you add resources and links that would be helpful for context here?
  3. Can you address https://github.com/FredHutch/gimap/pull/15/files#r1511607623 by adding information in the vignette?

Thanks! We're close!

Hey @cansavvy, would you be able to clarify point 3?

Can you address https://github.com/FredHutch/gimap/pull/15/files#r1511607623 by adding information in the vignette?

@cansavvy
Copy link
Collaborator

cansavvy commented Mar 7, 2024

@danieljgroso Yes! So this conversation: #15 (comment) If you can add information into the vignette that clarifies the terminology of T0 and etc and what time line is typical for this kind of data collection?

Copy link
Collaborator

@cansavvy cansavvy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for these adds! Let's merge this in!

@cansavvy cansavvy merged commit 1e7217e into main Mar 11, 2024
6 of 7 checks passed
@cansavvy cansavvy deleted the djg-vignette-review branch March 11, 2024 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants