Skip to content
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

ALTER POPULATION not available in Loom #625

Open
versar opened this issue Jul 19, 2018 · 1 comment
Open

ALTER POPULATION not available in Loom #625

versar opened this issue Jul 19, 2018 · 1 comment

Comments

@versar
Copy link

versar commented Jul 19, 2018

The following code:

%mml ALTER POPULATION data ADD VARIABLE cluster_1 nominal;

fails in Jupyter with the following behavior:

  • the standard output bar is colored pink, as for a warning
  • the standard output is blank and there is no error message

Even if Loom does not support adding iterations of ANALYZE, being unable to alter the population is still an issue because it is necessary for certain plotting workflows in exploratory data analysis. One example workflow is:

  • discovering a cluster using SIMILARITY
  • adding a cluster indicator column to the table and population
  • plotting that cluster indicator along with some data using interactive_pairplot

interactive_pairplot does not allow plotting a non-modeled variable, so the exploratory workflow above fails without the availability of ALTER POPULATION.

@fsaad
Copy link
Collaborator

fsaad commented Jul 20, 2018

The Loom backend does not have support for incremental updates such as adding/remove new rows or new variables. Trying to use ALTER POPULATION ... ADD VARIABLE ... causes a NotImplementedError to be thrown.

The reason that interactive_pairplot needs a population is to infer the stattypes. In terms of the plotting workflow you described for plotting one option is to create a new table and population that include the new column.

A second option is for us to extend the command line interface of interactive_pairplot so that it can take additional stattypes directly from the user.

(As for the Jupyter error message, it is capturing the stack trace from the NotImplementedError that was raised and is trying to print a succinct error message, although the error that is raised does not have custom message so you just see a pink output bar with no message.)

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

No branches or pull requests

2 participants