Garth Kong

Thank you Vince, we replaced all the large GIFs with still images (PNGs). Our BiocCheck run on our GitHub Actions looks dandy: https://github.com/maxsonBraunLab/CITEViz/runs/7717115756?check_suite_focus=true

I pushed my changes to GitHub, but I am confused about how to push my new changes to bioconductor's git repository. I tried to set my upstream using the command...

I'm going to pre-emptively address the warning that suggests me to evaluate more code chunks in the vignette. One code chunk is used to show the readers how to install...

Hi @PeteHaitch, I hope you were able to take a look at this package during the week. That last update was to replace devtools installation instructions with `BiocManager::install("CITEViz")`. How important...

Thank you @PeteHaitch for the initial review, I'll have a chat with my team to include support for SCE objects to provide interoperable software in BioConductor.

Hi @PeteHaitch, we are working to accept SCE objects into CITEViz. We plan to use a file format flag that determines how the data will be queried based on the...

Hi @PeteHaitch, we were able to include SCE objects to CITEViz! For some new functions we added, should we include the tests into the next commit? We will definitely finish...

Thank you for the additional comments! We have more documentation coming up soon, which should address most of the comments. I'll definitely rephrase the custom module sentence as it can...

I do have a general question about ExperimentHub and data sharing. I was wondering if it's ethically okay for us to publish another [EH package ](https://bioconductor.org/packages/3.15/bioc/vignettes/HubPub/inst/doc/CreateAHubPackage.html#building-the-package )if we didn't generate...

AdditionalPackage: https://github.com/maxsonBraunLab/CITEVizTestData