JMP® System Requirements
To view the system requirements for JMP®, JMP Pro, JMP Live, and JMP Clinical, click the following links: JMP system requirements for Windows operating systems JMP system requirements fo...
To view the system requirements for JMP®, JMP Pro, JMP Live, and JMP Clinical, click the following links: JMP system requirements for Windows operating systems JMP system requirements fo...
New in JMP/New Features documentation is published with the initial (.0) release of a new version of JMP and describes new or significantly enhanced capabilities introduced in that release. Re...
In JMP 15.0, when using by-groups or where clauses, the Nonlinear platform accesses the wrong rows in the data table for the X variables. It uses the row in the original table (rather than the row in the by-group) as it goes through the data, thus producing wrong answers without warning. This issue was fixed in maintenance release 15.1. [Previously JMP Note 65410]
This is a common issue caused by some parameters in the model becoming theoretically infinite. It can happen when the model perfectly predicts the response, or if there are more parameters in the model than can be estimated by the data (that is, with sparse data, where "sparse" means that there are few or no repeats of each setting of the covariates). One solution is to reduce the number of variab...
The following tables show the supported versions of JMP® and SAS® versions for each release of JMP Genomics and JMP Clinical. JMP Genomics JMP SAS10.115.1 (Pro) 9.4M7 10.015.1 (Pro) 9.4M6 9.113.2 9.4M5 9.013.2 9.4M5 8.212.29.4M48.112.29.4M38.012.19.4M37.111.29.4M27.011.19.4M16.110.0.29.3M26.010.0.09.3M1 JMP Clinical JMP SAS8.115.2.19.4M78.015.2.19.4M77.114.39.4M67.014.19.4M5 6.1 12.29.4...
When records in the SV domain have a missing value for Visit Number, an error occurs when running the Study Visits report. The hot fix for JMP Clinical 6.1 resolves this issue. Click on the link below to download the hot fix. JMP Clinical 6.1 Hot Fix [Previously JMP Note 62215]
If a study snapshot is updated with use of transport (.XPT) files, JMP® Clinical indicates the snapshot is successfully added, but errors occur when running reports such as Adverse Events Distribution and Findings Time Trends. An error might state the following: ERROR: There are no valid observations in the <XX> domain for analysis. Please check that your study data sets or any applied subject fil...
If a user attempts to rename a study that contains transport files, JMP® Clinical produces the following error: ERROR: File WORK.SDTMNOUSEDDOM.DATA does not exist. This issue is resolved in the JMP® Clinical 7.0.1 hotfix. [Previously JMP Note 63713]
If a study is renamed, the AE Review Flag in the Adverse Events Distribution report is set to "New" for every record. This issue is resolved in the JMP® Clinical 7.0.1 hotfix. [Previously JMP Note 63719]
The ANRIND variable conversion to xxNRIND for a reference range indicator is not accommodated in JMP® Clinical's support of ADaM Basic Data Structure (BDS), which affects the results in AE Narratives and Findings reports. This issue is resolved in the JMP® Clinical 7.0.1 hotfix. [Previously JMP Note 63707]
When a study contains only transport files, running Adverse Events Narrative with the default settings gives this error: ERROR: File SDTM.SUPPAE.DATA does not exist. This issue is resolved in the JMP® Clinical 7.0.1 hotfix. [Previously JMP Note 63712]
In JMP Clinical® 6.0, username length might cause the metadata table name to exceed the 32 character limit for SAS® data table names. Additionally, when JMP Clinical 6.0 is launched with a username containing the special character " – " only base JMP opens and the JMP Clinical menus do not appear. To resolve the errors, the user needs to extract the files from the zip file referenced below to the ...
Yes. Choose Analyze ► Multivariate Methods ► Multivariate, specify your continuous columns in the dialog box corresponding to the Y,Columns Role, and click OK to generate the analysis. In the analysis output window, click on the red triangle menu under the Multivariate header, and then select Item Reliability ► Cronbach's α, or Standardized α for Cronbach's α, standardized. [Previously JMP Note ...
Information on Stepwise Regression models containing nominal and/or ordinal effects can be found in the JMP® Fitting Linear Models documentation. In the Stepwise Regression Models chapter, see the section titled Models with Nominal and Ordinal Effects. [Previously JMP Note 36624]
Yes. Under Analyze ► Fit Model, construct a model such that the response column(s) is(are) modeled as Nominal or Ordinal, then select from one of several applicable Personality options, such as Nominal Logistic. Choose ROC Curve from the red triangle menu options under the model output. Note: ROC Curves are also available in other platforms in JMP, such as: Partition, Neural Net, and Discriminant....
JMP® uses the same seed selection method as the SAS® FASTCLUS procedure, with METHOD=FULL on the initial seeding. Generally, this method starts at observation one then chooses observations within the data set that are far apart. Please see the Background section for the FASTCLUS procedure in the SAS/STAT User's Guide for a detailed explanation. [Previously JMP Note 37931]
Yes, they are. From the Analyze ► Distribution window, click on the red triangle menu corresponding to a column of interest. In the resulting output window, select Display Options ► Customize Summary Statistics from the column's pull-down menu and check the box next to Geometric Mean, then Click OK. Alternatively, choose the Summary Statistics outline under the red triangle, select Customize Sum...
Using File > Print or Print Preview to view or create a JMP® report produce PDF images that are not properly sized. These images extend beyond the borders of the page and usually continue onto the next appropriate page. For example, the below graph was printed as a PDF report. Notice how this single image is split amongst the two pages. Figure 1 Workaround: save the report to Word then Print or ...
R 4.1.2 introduces R binary for Apple silicon arm (M1) chips. When JMP connects to the Application Response Management (ARM) build of R 4.1.2, JMP is unresponsive on the M1 Mac systems that are running Big Sur or Monterey. Note: This behavior is experienced running JMP natively or with Rosetta. It is recommended that you remove the R 4.2.1 ARM build and install R 4.1.2 for Intel, provided at https...
HTML5 reports that are produced from JMP show overlapping and improper layout display issues in the Google Chrome browser. This issue was first experienced after Chrome update 83.0.4103.61. It affects interactive HTML5 reports, JMP Public reports, and JMP Live reports. This issue is fixed in Chrome update 83.0.4103.97. [Previously JMP Note 66072]
When you install JMP and JMP Pro 17.0 via the SAS Software Depot, the license file located within the sid_files folder is not automatically applied. If you want to have the license file auto-applied during install, place the TXT license file that is located in the sid_files folder in the same folder as the jmp{pro}__1700__mac.dmg file. Then, run the installer. If you have any questions, contact JM...
When Minitab 19 or later is installed, JMP is unable to import Minitab files (.mtw files). Instead, an error message appears (for example, “Minitab 19 has stopped working”), and the Minitab program closes. The workaround is to install Minitab 18. [Previously JMP Note 67061]
The newest version of Google® Chrome (83.0.4103.61) has display issues with JMP® Graph Builder. The heading produced is too short and does not span the entire graph. Problems might occur when doing the following with Graph Builder: Exporting to Interactive HTMLPublishing to JMP PublicPublishing to JMP Live To fix the issue, close and reopen the disclosure icon (outline box) for Graph Builder. Go...
Apple announced that macOS 10.14 Mojave is the final release to support their Java SE 6 runtime. As a result, upgrading to macOS 10.15 Catalina causes JMP 14.1 and older versions to become unable to connect to SAS Metadata and Workspace servers. Upgrading to JMP 14.2 (or newer releases) corrects the issue. [Previously JMP Note 64964]
The JMP® Menu Editor leaves items from the Main Menu and Toolbars list active when selecting other items from the list. When making a change to a specific item any existing highlighted, items need to be selected once again to deactivate them. [Previously JMP Note 61973]
JMP® 17 is now available. The representative for all eligible JMP sites can request an upgrade from www.jmp.com/upgrade First and foremost, in order for the site representative to use the Software Upgrade Request application, the site must meet the eligibility criteria. These criteria include the following: The JMP product must be annually licensed.The JMP license must not be expired.The license m...
There are four ways that you can access JMP Technical Support: Telephone Support: You can receive telephone support by calling (800) 450-0135 between 9:00 AM and 5:00 PM Eastern Time.E-mail Support: You can communicate with SAS Technical Support by sending e-mail to support@jmp.com. You can send messages 24 hours a day, seven days a week. You can use this method to report new problems and supply ...