Subscribe Bookmark RSS Feed

Group scripts in themes in a data table?

Treponema

Occasional Contributor

Joined:

Nov 3, 2016

Hi Community,

 

I have searched in vain for a feature that can group scripts in my data table for an easy overview, just like this feature for grouping of columns: http://www.jmp.com/support/help/13/Group_Columns.shtml. My hope was to categorize my scripts in themes that are more or less always the same.

 

Is this possible at all?

 

Thanks!

2 ACCEPTED SOLUTIONS

Accepted Solutions
txnelson

Super User

Joined:

Jun 22, 2012

Solution
Scripts can not be grouped as columns can. It is a great idea, and I encourage you to send an enhancement request to support@jmp.com.

Jim
markbailey

Staff

Joined:

Jun 23, 2011

Solution

In the meantime, consider making a journal for your workflow instead of loading everyting into the small table panel. Journals are simple and versatile. You can organize the contents. The contents include text, URL, buttons with scripts, pirctures and so on.

Such a journal could include instructions and references with pictures. Buttons could initiate dialogs to collect user choices or data tables from templates. Other buttons could run scripts on the current data table.

It is pretty much limited only by your imagination.

10 REPLIES
txnelson

Super User

Joined:

Jun 22, 2012

Solution
Scripts can not be grouped as columns can. It is a great idea, and I encourage you to send an enhancement request to support@jmp.com.

Jim
Treponema

Occasional Contributor

Joined:

Nov 3, 2016

Thank you for the response, I have sent a request to support@jmp.com :)

dr_winfried_koc

Community Trekker

Joined:

Nov 5, 2014

I support this request because groupring of scripts would be helpful for my workflow too.

 

Winfried

ih

Contributor

Joined:

Sep 30, 2016

If you have a lot of scripts that you run on the same data table you might consider combining them into one script and adding a box with buttons or links to run each script. That way you can organize them however you wish and give a description for each.

Treponema

Occasional Contributor

Joined:

Nov 3, 2016

Hi Isaac,

 

That is a good way to go usually, but I in this instance I am trying to build a data exploration script library on (R&D) cell culture data. The data is designed to be in the same format across systems, users, etc. Since no experiment is alike, the scripts are used according circumstances.

 

I would like to be able to 'build' a dummy-data table with script-categories for 'cell growth', 'metabolism' etc. - the user should therefore be able to copy paste from the dummy data table to their own data table. Users are not necessarily well-versed in JMP, thus this strategy.

 

Thanks for the reply :)

 

markbailey

Staff

Joined:

Jun 23, 2011

Solution

In the meantime, consider making a journal for your workflow instead of loading everyting into the small table panel. Journals are simple and versatile. You can organize the contents. The contents include text, URL, buttons with scripts, pirctures and so on.

Such a journal could include instructions and references with pictures. Buttons could initiate dialogs to collect user choices or data tables from templates. Other buttons could run scripts on the current data table.

It is pretty much limited only by your imagination.

Treponema

Occasional Contributor

Joined:

Nov 3, 2016

Thank you - Journals are indeed versatile and that is what I am using at the moment. I think I may have to practice a bit more with them :)

markbailey

Staff

Joined:

Jun 23, 2011

I am surprised by how many JMP users have never even heard of the journal feature. Those users who have heard of them often consider them only as a place to save results. They are certainly good for that purpose. They can be so much more, however. We started using them in our JMP training courses over a decade ago as a superior way to provide all the course materials besides the course notes themselves. The fact that we could click a button to run a script also provide a straight-forward means to introducing Monte Carlo simulations in the lessons. The journal organizes everything exactly the same way as the course notes (book) by chapter and section. Students open the book and the journal at the start of class and proceed through both of them. Simple but intuitive and effective.

I think that the example of how we use journals in our own training can be extended in myriad ways to many other situations.

ih

Contributor

Joined:

Sep 30, 2016

A Journal is a great way to go.  Now that I understand more of what you are doing though I think an add-in is what you are looking for.  You can organize your scripts in the same way you would add them to the JMP software.  Users would not need to copy scripts to their own tables, therefore they are less likely to have old versions of your scripts buried in their files.  One update to their add-in and everything you ever write is up-to-date, plus they get all of your new stuff.