Documenting my work flow

Question

I am a new JMP user.   I am a scientist who is analyzing data that I am retrieving from several sources and using JMP, along with other tools, to explore the compiled data.    I have some experience in data management, data analysis and statistic but no formal training in these fields.  I am looking for suggestions on how others record (document) their workflow when using JMP as one of the tools in their work stream.

Have you found either JMP journal or notebook to be adaptable to this need?  Is something like Juypter, even though I am not coding, a better solution?  Any suggestions are appreciated!!

shaneline · Answer

Hi,

Thanks again!   Yes. I am running JMP 14, so I will start with JMP Projects and go from there.

The JMP Application sounds handy for the future.   Over the past few years, I was creating monthly routine reports (dashboards) during the data collection phase.   Now the data collection has been completed, locked, and the planned statisitcal anlysis has been completed my efforts are more exploratory;hence, the need to be more rigourous in documenting my work.

Once I get a routine down,  would it be worth posting about it here for others?

P_Bartell · Answer

My inital reply assumed you were running JMP 14...if that's the case, I think your workflow makes sense to me. Others may chime in with better/more efficient ideas. If you are running an earlier version of JMP then I'm thinking just embedding everything in a journal might be a more efficient way to go. JMP Project capability was very much completely revamped in version 14.

And not to get too sophisticated but one other capability you may want to look at are JMP Applications. JMP Applications are not unlike building an app for any work task, that can be automated or made easier to use. JMP users commonly build applications for one of two reasons; 1. To automate a workflow for folks that aren't sophisticated JMP users, but they do repetitive analysis/reporting/sharing/distributing, and the application, if built properly makes the worlflow both standard and more mistake proof. 2. Maybe JMP can't do something out of the box, but the user community needs that capability in an easy to use interface...the JMP application is a script or collection of scripts that executes this workflow in an efficient manner.

shaneline · Answer

Thank you for the feedback!!

I have started to review some of the different online resources but thought best to ask for advice here first so that I could have a better focus on how I might use these tools to complete my task.  My goal is to have an overall process in mind so that as I use the JMP resources I might more quickly understand how they should be used together.

So, is it fair to say that in order to document my work an overall process would be to?

* Begin by creating a Project
* Take any action that might be needed (sounds like none is needed) to ensure I will record the JSL code.
* Begin a journal to record the text (documentation) normally captured in a lab notebook (purpose, background, source material, method,  interim results and decisions, etc.;)
* Performing any work needed to complete my task by writing to the journal as I proceed.
* Capturing the JSL code within the Journal
* Capturing the journal in the project
* Ensure all is saved to the Project

It also sounds as if I will also be able to record those actions, I take outside of the JMP platform as well (minus the JSL code recording equivalent for those steps).

Again.  Thank you for the advice!!