Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@hillarymarler
Copy link
Collaborator

When a data set had no depth data available, the additional columns, TADA.DepthCategory.Flag and TADA.ConsolidatedDepth, were not added. This created problems in some workflows. This fix adds the two columns (filled with NA) when a data set has no depth data available.

hillarymarler and others added 2 commits July 7, 2025 16:48
Depth.count ==0 was inside depth.count>0, moved the if chunk outside of it. specified the NA as a character and numeric for TADA.DepthCategory.Flag and TADA.ConsolidatedDepth respectively.
@wokenny13
Copy link
Collaborator

I made a minor update in my commit. This seems to resolve the problem for cases in which no depth data is available.

@cristinamullin cristinamullin self-requested a review July 9, 2025 18:09
R/DepthProfile.R Outdated
}

if (depth.count == 0) {
print(paste0("TADA_FlagDepthCategory: checking data set for depth values. No results have depth values available. ",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is paste needed here?

Suggested update:

print("TADA_FlagDepthCategory: No depth information was found in the dataset. The columns TADA.DepthCategory.Flag and TADA.ConsolidatedDepth are being added and populated with NA values.")

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I removed the unnecessary paste, @cristinamullin. Thanks!

@cristinamullin cristinamullin merged commit 1c4eb4f into develop Jul 10, 2025
3 of 7 checks passed
@cristinamullin cristinamullin deleted the flagdepth branch July 10, 2025 15:47
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.

4 participants