Peut exécuter la fonction à partir du menu de dégradation, mais lors de l'enregistrement du script dans la table de données (ou la fenêtre de script) et de son exécution, l'ensemble de jmp 17 se fige et doit être tué.
pas de problème de ce type dans jmp 16.
ci-joint le tableau de données.
Utilisez-vous JMP 17.1 ? Je peux confirmer que le script enregistré dans la table de données que vous avez fournie provoque le blocage de JMP. Le script que JMP a créé pour moi en 17.1 a une syntaxe supplémentaire qui ne figurait pas dans votre table de données (et n'entraîne pas de comportement de blocage). Code ci-dessous :
/*JMP STATISTICAL DISCOVERY LLC (“JMP”) PERMITS THE USE OF THIS COMPUTER SOFTWARE CODE (“CODE”) ON AN AS-IS BASIS AND AUTHORIZES YOU TO USE THE CODE SUBJECT TO THE TERMS LISTED HEREIN. BY USING THE CODE, YOU AGREE TO THESE TERMS. YOUR USE OF THE CODE IS AT YOUR OWN RISK. JMP MAKES NO REPRESENTATION OR WARRANTY, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NONINFRIGEMENT, AND TITLE, WITH RESPECT TO THE CODE.
You may use the Code solely as part of a software product you currently have licensed from JMP, JMP’s parent company SAS Institute Inc. (“SAS”), or one of JMP’s or SAS’s subsidiaries or authorized agents (the “Software”), and not for any other purpose. The Code is designed to add functionality to the Software but has not necessarily been tested. Accordingly, JMP makes no representation or warranty that the Code will operate error-free. JMP is under no obligation to maintain, support, or continue to distribute the Code.
Neither JMP nor its licensors shall be liable to you or any third-party for any general, special, direct, indirect, consequential, incidental, or other damages whatsoever arising out of or related to your use or inability to use the Code, even if JMP has been advised of the possibility of such damages. Except as otherwise provided above, the Code is governed by the same agreement that governs the Software. If you do not have an existing agreement with JMP or SAS governing the Software, you may not use the Code.
JMP and all other JMP Statistical Discovery LLC product or service names are registered trademarks or trademarks of JMP Statistical Discovery LLC in the USA and other countries. ® indicates USA registration. Other brand and product names are registered trademarks or trademarks of their respective companies.
*/
Degradation(
Y( :data ),
Time( :MONTHS ),
Label( :BATCH ),
Upper Spec Limit( 105 ),
Lower Spec Limit( 95 ),
Application( Repeated Measures Degradation ),
Connect Data Markers( 1 ),
Show Fitted Lines( 1 ),
Show Spec Limits( 1 ),
Show Median Curves( 0 ),
Show Legend( 1 ),
No Tab List( 0 ),
Use Pooled MSE for Nonpoolable Model( 0 ),
Set Censoring Time( . ),
Show Residual Plot( 1 ),
Show Inverse Prediction Plot( 1 ),
Inverse Prediction Interval( No Interval ),
Inverse Prediction Alpha( 0.05 ),
Path Specifications(
Simple Linear(
Add Custom X Scale(
{{"Linear", Function( {x}, x ), Function( {x}, x )}}
),
Add Custom Y Scale(
{{"Linear", Function( {x}, x ), Function( {x}, x )}}
),
Slope( Different ),
Intercept( Different ),
Select X Scale( "Linear" ),
Select Y Scale( "Linear" )
),
Nonlinear Path
),
Simple Linear Path( 1 ),
Mean Path( 1 )
);
Merci d'avoir soulevé cette question. Il s'agit d'un problème connu dans JMP17 et 17.1. Il a été corrigé en 17.2. Veuillez effectuer la mise à niveau lorsque la version 17.2 sera disponible.
