Welcome to oce Discussions!

[dankelley]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[dankelley]

I'm Dan Kelley, a Physical Oceanographer at Dalhousie university and a co-author of the oce package. (Shameless plug: I also have a book that might interest oceanographers: Kelley, Dan E. Oceanographic Analysis with R. New York: Springer-Verlag, 2018. https://www.springer.com/us/book/9781493988426.)

I do the majority of oce coding, and I monitor the issues regularly, although on the latter I probably am not as helpful as @richardsc.

[coffm049-2]

Hi there! I'm newer to using CTD-esque data. I'm working with some data that reports the variable "specc" which corresponds to the long name "Specific Conductance".

Using the oce package I see that this column automatically gets mapped to "Conductance" (as reported in line 156 of this file.

Is there any easy way for me to solve this? I was planning on forking and using my own version with a very slight change to account for this.

Thank you,
Christian

[richardsc]

And to clarify, I think that the issue could be boiled down to:

"specc" is incorrectly converted to "conductivity", but should be "specificConductance"

[coffm049-2]

Yes no problem. I'll go ahead and transfer it over to Issues.

[dankelley]

If it's an error, we can change oce, of course. I must have inferred that this was a type of conductivity from some manual. Note that if it's wrong, then perhaps the unit is wrong also, and that would mean a few more lines to change.

PS. the code I sent will work whether the file has that variable or not, as shown below

a <- data.frame(a=1:3, b=10:12)
str(a)
#> 'data.frame':    3 obs. of  2 variables:
#>  $ a: int  1 2 3
#>  $ b: int  10 11 12
n <- names(a)
# This won't change anything...
n[n == "c"] <- "will not happen"
names(a) <- n
str(a)
#> 'data.frame':    3 obs. of  2 variables:
#>  $ a: int  1 2 3
#>  $ b: int  10 11 12

# ... but this does.
n[n == "b"] <- "new b"
names(a) <- n
str(a)
#> 'data.frame':    3 obs. of  2 variables:
#>  $ a    : int  1 2 3
#>  $ new b: int  10 11 12

^{Created on 2024-05-02 with reprex v2.1.0}

[dankelley]

I see that is is an error (see below from an SBE manual) and I'll make the fix once I see an issue. I can also set up the issue myself but it's nice to see issues from users.

[coffm049-2]

Thank you for checking up on this! I've made the issue

#2211 (comment)