-
Notifications
You must be signed in to change notification settings - Fork 2
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
Check for OR SP samples #48
Comments
It was never passed as input, it is a data object that all functions have access to. Though, we could remove it I think because the last time I checked PacFIN had corrected those samples in their data base. I would want to remove the data object as well. |
Thank you for the clarification. I had thought I remembered this being an input to the function in 2019, but that might not have been correct. I now see that the badORnums are loaded into the workspace. I won't close this issue at this moment so we can use it as a reminder for us to remove this check and objects from the package later. |
That was for Owen, a one-off.
…On Tue, Feb 16, 2021 at 1:22 PM Chantel Wetzel ***@***.***> wrote:
Thank you for the clarification. I had thought I remembered this being an
input to the function in 2019, but that might not have been correct. I now
see that the badORnums are loaded into the workspace. I won't close this
issue at this moment so we can use it as a reminder for us to remove this
check and objects from the package later.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACTUYBXIPKXGFLCID4XG2H3S7LOYNANCNFSM4XXDXG4A>
.
|
These samples were noticed as being incorrectly labeled during the 2019 sablefish assessment. And, I just checked PacFIN and some of these samples still are not listed as SP instead of O. So, we should keep the check. |
|
@aliwhitman there are OR sablefish samples that are Special Project samples labeled as Market samples in PacFIN. Some have been changed to SP but not all. How do we go about fixing the remainder? Here is a list of sample numbers, though some have been fixed. |
I'm happy to check on this but I am confused - how can they be labeled as both SP and Market samples in PacFIN? |
They are labeled M but they should be labeled SP. |
Still confused - sorry! perhaps the right question is why should they be labeled SP? But I will send the sample numbers to our data shop for them to fix and then resubmit to PacFIN. And I'll give you an ETA when we have them fixed! |
@aliwhitman check your email for a string with [email protected] from March of 2019 as well as the email I just forwarded. |
Gotcha. Thank you! Our data shop are on it, they'll provide updates and I know you need those data ASAP, so I'll stay on it. |
https://github.com/nwfsc-assess/PacFIN.Utilities/blob/562be10030cc252fc8bbf8ce2b9b7833f6a9e191/R/cleanPacFIN.R#L295
I think this line of code can be removed since "badORnums" is no longer being passed as an input to the function.
The text was updated successfully, but these errors were encountered: