Warn me if executing a command / running an analysis is going to take a long time.

[parker]

I find on larger data sets that some analyses take a long time to run.  For example, running a Binomial or Poisson generalized linear model on a data set with ~20 million rows can take over an hour on my machine.  It would be great if JMP could (1) warm me if executing a command was going to take longer than 10 minutes and give me the option to cancel; and (2) if I choose to continue, give me an estimate of how long the analysis was going to take to complete.

[jwiltsie]

Or could be a status bar with an option to cancel for platforms that involve potentially difficult analyses. Like what is implemented in the custom design platform.

[john_madden]

It would also be nice if there were a JSL busy widget (a.k.a. wait widget, spinning wheel widget, etc.) that could be used to give the user assurance that a script is still executing. Even better would be a JSL progress bar widget.

[vince_faller]

Often Pushing Esc during the run will cancel the platform.  It will take a 5-15 seconds to respond usually but it normally works.  

Try this:

names default to here(1);
dt = open("$SAMPLE_DATA\Probe.jmp");
g = dt << Get Column Group("Responses");
YExpr = Expr(Y());
for(i=1, i<=nitems(g), i++, 
	insert into(YExpr, g[i]);
);
Eval(EvalExpr(
	dt << Hierarchical Cluster(
		Expr(nameexpr(YExpr)),
		Method( "Ward" ),
		Standardize Data( 1 ),
		Dendrogram Scale( "Distance Scale" ),
		Number of Clusters( 20 ),
		SendToReport( Dispatch( {}, "Dendrogram", OutlineBox, {SetHorizontal( 1 )} ) )
	);
));

[SamGardner]

Delivering this capability will need to be on a platform-by-platform basis, but we have created an overall tracking category for this type of issue and will be working on improving the user experience when this occurs.  

[hogi]

Agree, for user defined scripts there is the easy solution by @vince_faller to press ESC long enough till it stops.
But for standard platforms this doesn't work. So, along the idea of the wish:

---

@parker wrote:

warm me if executing a command was going to take longer than 10 minutes and give me the option to cancel

---

but independent of the warning:

 every standard platform should have a cancel button while running.
This way, a user will have the option top stop a platform whenever he wants - no need to wait hours and hours till a platforms finishes.
Speed up Tables/Update 

[hogi]

alternative idea: a Timeout setting in the preferences or a timeout option for Try.

[hogi]

candidate of the Wish List Prioritization Survey - pilot run:
Introducing the JMP Wish List Prioritization Survey! 

[hogi]

For several platforms I could identify the root cause of a slow execution - avoiding these trapdoors can save you hours:

1. Speed up Tables/Update : for every column, it scans again for the matching rows and merges ALL matches into the main table.
   -> rows x # matches x  # columns
   instead of 1x last first or last match (like in Tables / Join)
   -> can take hours instead of seconds
   - the GUI starts with all options enabled
   - the preview
   
   
2. Why is Tables/Concatenate so slow? 
   new issue in JMP18: it takes extremely long time to scan the Table Scripts.
   And the platform scans the table scripts while creating the GUI, when a user adds a table and a last tie when the user clicks on OK
   -> can take several second to minutes
   
   
3. Re: Recode - Parse as Number 
   if a user executes multiple steps and converts a string into a number it takes much more time than doing the same in 2 steps
   -> can take minutes to hours

[hogi]

Live Distribution: it's very slow if the table has many thousand rows.

new (in JMP18?) : if many rows belong to one value, JMP can "bundle" the values -> less points in the pot and much (!!!) faster