Currently, reasons for stattype guesses are encoded as comments enclosed in triple quotes.
This format assumes the user will be using a triple quote string within a bdb.execute() command to create a population with the schema.
With quotes, the schema text cannot be directly copy/pasted into an MML block with iVenture. There seems to be no way to include the reasons such that an MML cell in a Jupyter notebook could ignore them on execution.
Two potential plans for improving this:
Modify MML such that there are two options: GUESS SCHEMA FOR <table> and GUESS SCHEMA FOR <table> WITH REASONS.
Make GUESS SCHEMA FOR <table> create a new table in the bdb with three columns: column, guessed_stattype, and reason. Then, the user could edit stattypes by modifying the table. We would need to add an additional MML command such as PRINT SCHEMA STRING to convert the table to a string that could be copied and pasted into a CREATE POPULATION command.
Currently, reasons for stattype guesses are encoded as comments enclosed in triple quotes. This format assumes the user will be using a triple quote string within a bdb.execute() command to create a population with the schema. With quotes, the schema text cannot be directly copy/pasted into an MML block with iVenture. There seems to be no way to include the reasons such that an MML cell in a Jupyter notebook could ignore them on execution.
Two potential plans for improving this:
GUESS SCHEMA FOR <table>andGUESS SCHEMA FOR <table> WITH REASONS.GUESS SCHEMA FOR <table>create a new table in the bdb with three columns: column, guessed_stattype, and reason. Then, the user could edit stattypes by modifying the table. We would need to add an additional MML command such asPRINT SCHEMA STRINGto convert the table to a string that could be copied and pasted into aCREATE POPULATIONcommand.