puki.or gwas built collaboratively between people in data, statistics, and application development. If you like this platform or perhaps more importantly if there is something you don't like about JMS, change it. Don't like the color scheme? Change the style sheets. Don't like decomposition output? Change the report. It's designed to be flexible. puki.org hinges on data integrity. Databases are better at maintaining data integrity than analysts. JMS is designed to keep all data registered and “in the system.” What this means is that from squaring off a model, to reviewing the data in it, to generating a model and running reports for ROI, effectiveness, and simulated response, throughout that entire chain of events, the analyst does not have to touch or manipulate data. Analysts are better at interpreting the data. For that reason, a great deal of overhead goes into the data upfront. Spend needs to be “in system”. Profit margins need to be “in system”. Projection factors need to be “in system”. The benefit of all this overhead is simple: maximize the time analysts have for interpretation by minimizing the amount of data intervention required. Read more about data integrity in discussion of mast data sets.