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.
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
Refactor
met.process
anddbfiles
#3319Refactor
met.process
anddbfiles
#3319Changes from 9 commits
f9a0cff
dd53e34
2a9e286
45a7019
7214403
a61d38e
3509396
da6955a
36b661a
3eddf58
3314842
afaf73f
0b3d0c4
e36396f
978309a
604e03f
f665ed8
d33631c
cbfb7c1
9f9dc73
23c7809
4ffd0db
c276f78
383443c
4f9320e
e9367b5
3ff0eb3
7ff5dce
60be255
49502b9
8405afb
665a5ec
4d37521
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this changes behavior: previously
ready.id
would have an entry for each id whether it was standardized or not; this only adds the ids that were standardized. Is that intentional?(As currently implemented I think ids not standardized would probably have errored out earlier, but this step should not rely on that)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've implemented a
NA
appending too to make sure to append even when we have face a!is_standardized
condition. The initial though process I had was whether it would be wise pass theinput.id
's to.met2model.module
and later on toconvert_input
if we have not standardised our results. Although it seems I failed and ignored the order in array at check which may change the results.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@infotroph Can you take a look into this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Sweetdevil144 I was wrong above about the existing behavior -- In the current code
standardize_result
has an entry for each id, but it is NULL for ids not standardized and therefore gets silently dropped when appending toready.id
. I don't know how advisable that is, but I bet downstream code relies on it.I'll suggest changes here that eliminate the second for-loop but keep the original behavior -- please edit further if you see problems I missed.