-
Notifications
You must be signed in to change notification settings - Fork 38
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
Change bulk upload (via wizard or API) to allow for traits not in the trait_covariate_associations table #459
Comments
Changes for the API have been implemented (but not deployed). This changes the API behavior as follows. [From issue #193:]
In addition, it is an error if there is a variable name listed in the heading that corresponds to a covariate in the |
…rd (issue #459) and removed "pending" from related tests.
Fixed by release 4.15. |
Re-opening. This feature is not yet working properly. |
@dlebauer I made a note that this was not yet working properly, but I don't remember who reported this or any other details. |
If I have a csv upload with a column name that matches a name in the
variables table, it should insert the values into the traits table. The
absence of a covariate is irrelevant.
The traits covariates associations table is useful when there is a
covariate. But it should not prevent inserting variables that do not
require a covariate.
…On Fri, Jun 2, 2017 at 5:34 PM Scott Rohde ***@***.***> wrote:
Assigned #459 <#459> to
@dlebauer <https://github.com/dlebauer>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#459 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAcX55N3sIJNad7HFeTt7DmIcNXsiNCIks5sAIVrgaJpZM4Ku4-->
.
|
…izard or API) to allow for traits not in the trait_covariate_associations table") Improved efficiency by taking some one-time computations outside of a loop.
…the feature in issue #459 is working. Also tweaked the test to get it working properly.
See terraref/computing-pipeline#193 (comment) for discussion of how this should work.
The text was updated successfully, but these errors were encountered: