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

Develop #494

Merged
merged 170 commits into from
Jan 27, 2025
Merged

Develop #494

merged 170 commits into from
Jan 27, 2025

Conversation

kathy-nevola
Copy link
Contributor

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:

  • Key feature 1
  • Key feature 2
  • ...

Checklist

  • Make sure you are requesting to pull a feature/bugfix branch (right side). This should not be main or develop.
  • Make sure you are make a pull request against either main or develop (left side). (Requesting to main should be reserved for bugfixes and new releases)
  • Add or update unit tests (if applicable)
  • Check your code with any unit tests (Run devtools::check() locally)
  • Add neccessary documentation (if applicable)

Type of changes

What type of changes does your code introduce?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue) (link the issue on the right)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Code style update (formatting, renaming)
  • Documentation Update
  • Other (explain)

Further 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.

klevdiamanti and others added 30 commits October 1, 2024 10:41
…ackages in the code. Also added function documentation
Merge branch 'develop_3k-HT_plots' of github.com:Olink-Proteomics/OlinkRPackage into develop_3k-HT_plots

# Conflicts:
#	OlinkAnalyze/man/bridgeable_plts.Rd
…k_normalization_product_format is run. Add argument to olink_normalization to toggle whether formatting is applied.
…k-Proteomics/OlinkRPackage into develop_product_bridging_downstream
…so added a median of negative controls for approximate LOD in the correlation plot.
Co-authored-by: Kathy Nevola <72228735+kathy-nevola@users.noreply.github.com>
Co-authored-by: Kathy Nevola <72228735+kathy-nevola@users.noreply.github.com>
dtopouza and others added 29 commits January 24, 2025 13:12
…g_downstream

Convert output of cross-product bridge to be used in downstream functions
update Description and news for v4.1
…ates_KC

Revert "Vignette Updates - Simplifying Existing Vignette"
@kathy-nevola kathy-nevola merged commit 1257ed4 into main Jan 27, 2025
16 of 17 checks passed
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.

7 participants