turn on suggestions

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

Showing results for

- JMP User Community
- :
- Discussions
- :
- Discussions
- :
- What is meant by JMP Alert - Profiler will be fast...

Topic Options

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page

Highlighted

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(187 views)

I am creating a fairly messy reliability block diagram in JMP Pro, so I'm using Library Items to keep my top level Design Diagram cleaner. As I add parallel redundancies within my Library Item, which is then used multiple times in parallel redundancies in my Design Diagram, things really slow down and eventually stop. Prior to JMP stopping, I received the JMP Alert "Profiler will be faster by decreasing Default N Levels." I could not figure out what that meant or how to do it. Any suggestions?

Thanks! Don

Solved! Go to Solution.

1 ACCEPTED SOLUTION

Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(225 views)

Solution

These are what I can think of:

1) Under the "Start" block, there is a check box "Run". Uncheck it, so you can continue editing the diagram, but the calculation will not be carried out on the fly. Check the box, after finishing editing the diagram.

2) If the parallel redundant components are identical, use the built-in "Parallel" block. If the parallel redundant components are sub-systems, there is no way to put sub-system in "Parallel" block for now. A workaround is to use the "Nonparametric" distribution in "Parallel". First come up with a data set, whose nonparametric estimate of the distribution is close to the distribution of the subsystem. Then feed that data to Nonparametric distribution in "Parallel" block. Coming up with the data set is not a trivial task.

3) Use "Repairable Systems Simulation" platform. The "Point Estimation of System Availability Profiler" is the reliability function, if no maintenance is involved. This approach is slower for small systems, but more feasible for large systems. However this platform focus on different metrics, and does not provide the same set of graphs as those in "Reliability Block Diagram" platform. Also this platform does not support sub-system yet.

7 REPLIES

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(156 views)

outside of my area...but I found this example in the scripting index

Craige

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(134 views)

The curves in the Prediction Profiler are formed by evaluating the the prediction formula a number of times for each factor across the range of the factor while holding the other factors constant at their current values. These points are then connected to form the curve. The number of times the formula is evaluated for each factor is controlled by the Default N Levels option under the red triangle.

From the help page:

Default N Levels

Enables you to set the default number of levels for each continuous factor. This option is useful when the Prediction Profiler is especially large. When calculating the traces for the first time, JMP measures how long it takes. If this time is greater than three seconds, you are alerted that decreasing the Default N Levels speeds up the calculations.

-Jeff

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(125 views)

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(120 views)

Yes, the Distribution outline node in the Reliability Block Diagram is actually a Prediction Profiler.

It sounds like you do have a really big, complicated diagram that JMP is having difficulty with. Tech Support is best positioned to help figure out if there's anything that can be done to speed it up.

-Jeff

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(226 views)

These are what I can think of:

1) Under the "Start" block, there is a check box "Run". Uncheck it, so you can continue editing the diagram, but the calculation will not be carried out on the fly. Check the box, after finishing editing the diagram.

2) If the parallel redundant components are identical, use the built-in "Parallel" block. If the parallel redundant components are sub-systems, there is no way to put sub-system in "Parallel" block for now. A workaround is to use the "Nonparametric" distribution in "Parallel". First come up with a data set, whose nonparametric estimate of the distribution is close to the distribution of the subsystem. Then feed that data to Nonparametric distribution in "Parallel" block. Coming up with the data set is not a trivial task.

3) Use "Repairable Systems Simulation" platform. The "Point Estimation of System Availability Profiler" is the reliability function, if no maintenance is involved. This approach is slower for small systems, but more feasible for large systems. However this platform focus on different metrics, and does not provide the same set of graphs as those in "Reliability Block Diagram" platform. Also this platform does not support sub-system yet.

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(110 views)

Thank you for all the helpful replies! I greatly appreciate your time.

I tried just unselecting Show Distribution Profiler to speed things up, but calculations were still apparently taking place behind the scenes. Unchecking the Run button did the trick, although when I eventually recheck it the calculations still take quite a while to run, even with N = 3. After the initial calculations, slowly increasing N to 7 and then to 15 resulted in much faster calculations. I did get rid of the Library object in my diagram (another complex parallel series system) and replaced it with K out of N blocks as approximations (not perfect, but still useful). That seems to prevent JMP from crashing. I attached a similar diagram showing the complexity, just for reference. It may be the networking-style of redundancies that are taking a while to calculate. I certainly could never calculate them by hand. Thank goodness for JMP Pro!

- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content

2 weeks ago
(101 views)

Glad that helps. And thanks for the example. The example will help for future improvement.