-
Notifications
You must be signed in to change notification settings - Fork 23
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
Optimization develop #380
Merged
klevdiamanti
merged 74 commits into
opt_dev_checknpx_internal_funcs
from
optimization_develop
May 31, 2024
Merged
Optimization develop #380
klevdiamanti
merged 74 commits into
opt_dev_checknpx_internal_funcs
from
optimization_develop
May 31, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Optimization develop to develop
add missing globals
Decrease vignette size
Release to main
Adjust expected name of parquet metadata "Product"
Add support for export from internal R package for Explore HT data
Update news and description for 3.5.1
Bugfix release Parquet Metadata
…github.com/Olink-Proteomics/OlinkRPackage into 290-mulitple-flags-in-normalization-column
…llow R 4.1.3 to work
3.6 release
Klevdiamanti patch 1
…cs/OlinkRPackage into optimization_main
…untu_24.04 Optimization develop ubuntu 24.04
Include 'optimization_main' to CI to mirror 'main'
Merge branch 'optimization_main' of https://github.com/Olink-Proteomics/OlinkRPackage into optimization_develop_read_npx_to_main # Conflicts: # .github/workflows/R-CMD-check.yaml # OlinkAnalyze/DESCRIPTION # OlinkAnalyze/NEWS.md # OlinkAnalyze/R/Olink_bridgeselector.R # OlinkAnalyze/R/Olink_normalization.R # OlinkAnalyze/R/Read_NPX_data.R # OlinkAnalyze/R/globals.R # OlinkAnalyze/R/npxProcessing.R # OlinkAnalyze/R/pca_plot.R # OlinkAnalyze/R/read_npx_csv.R # OlinkAnalyze/R/read_npx_parquet.R # OlinkAnalyze/inst/extdata/npx_data_ext.parquet # OlinkAnalyze/tests/testthat/_snaps/Read_NPX_data.md # OlinkAnalyze/tests/testthat/test-Olink_normalization.R # OlinkAnalyze/tests/testthat/test-npxProcessing.R # OlinkAnalyze/tests/testthat/test-olink_normalization_n.R # OlinkAnalyze/tests/testthat/test-pca_plot.R # OlinkAnalyze/vignettes/OutlierExclusion.Rmd # OlinkAnalyze/vignettes/Vignett.Rmd # OlinkAnalyze/vignettes/bridging_introduction.Rmd # OlinkAnalyze/vignettes/plate_randomizer.Rmd
…ad_npx_to_main Optimization develop read npx to main
Optimization main
check_npx_col_names to optimization_develop
klevdiamanti
merged commit May 31, 2024
f5688c5
into
opt_dev_checknpx_internal_funcs
9 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Title: Write a very short summary here
Problem: Write a description of your problem here.
Solution: Write a short summary of your solution.
Key Features:
Checklist
Type of changes
What type of changes does your code introduce?
Put an
x
in the boxes that applyFurther comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, any questions you have, etc...
Consider linking any issues (#issue-number ) or adding @mentions to ensure specific people see it.