I have a question concerning layouts in JMP. I am running equivalence tests between difference lasers (9 unique results) to ensure that they perform the same. When I run the script, it returns a stack of about 36 different graphs in no particular order. What I would like to do is something similar to what has been done with an R script before in which graphs were laid out in a matrix where corresponding equivalence graphs between the two lasers are easily located in the grid, like so: Header 1Laser 1Laser 2Laser 3Laser 4Laser 5Laser 1Blank L2 v L1 Equivalency GraphL3 v L1 Equivalency GraphL4 v L1 Equivalency GraphL5 v L1 Equivalency GraphLaser 2L1 v L2 Equivalency GraphBlankL3 v L2 Equivalency GraphL4 v L2 Equivalency GraphL5 v L2 Equivalency GraphLaser 3L1 v L3 Equivalency GraphL2 v L3 Equivalency GraphBlankL4 v L3 Equivalency GraphL5 v L3 Equivalency GraphLaser 4L1 v L4 Equivalency GraphL2 v L4 Equivalency GraphL3 v L4 Equivalency GraphBlankL5 v L4 Equivalency GraphLaser 5L1 v L5 Equivalency GraphL2 v L5 Equivalency GraphL3 v L5 Equivalency GraphL4 v L5 Equivalency GraphBlank I've tried using the layout editor to to it manually, but this method is unreliable, ineffecient, and not easily replicable through scripting. If anyone has any input on either an array graph script or means of scripting this to work, it would be much appreciate. -Will

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating a matrix of graphs

wgoth

I have a question concerning layouts in JMP. I am running equivalence tests between difference lasers (9 unique results) to ensure that they perform the same. When I run the script, it returns a stack of about 36 different graphs in no particular order. What I would like to do is something similar to what has been done with an R script before in which graphs were laid out in a matrix where corresponding equivalence graphs between the two lasers are easily located in the grid, like so:

Header 1	Laser 1	Laser 2	Laser 3	Laser 4	Laser 5
Laser 1	Blank	L2 v L1 Equivalency Graph	L3 v L1 Equivalency Graph	L4 v L1 Equivalency Graph	L5 v L1 Equivalency Graph
Laser 2	L1 v L2 Equivalency Graph	Blank	L3 v L2 Equivalency Graph	L4 v L2 Equivalency Graph	L5 v L2 Equivalency Graph
Laser 3	L1 v L3 Equivalency Graph	L2 v L3 Equivalency Graph	Blank	L4 v L3 Equivalency Graph	L5 v L3 Equivalency Graph
Laser 4	L1 v L4 Equivalency Graph	L2 v L4 Equivalency Graph	L3 v L4 Equivalency Graph	Blank	L5 v L4 Equivalency Graph
Laser 5	L1 v L5 Equivalency Graph	L2 v L5 Equivalency Graph	L3 v L5 Equivalency Graph	L4 v L5 Equivalency Graph	Blank

I've tried using the layout editor to to it manually, but this method is unreliable, ineffecient, and not easily replicable through scripting. If anyone has any input on either an array graph script or means of scripting this to work, it would be much appreciate.

-Will

Accepted answers

David_Burnham

You could try taking a look at the SheetBox display box

All comments

David_Burnham

You could try taking a look at the SheetBox display box

wgoth

Thanks Dave, exactly what I was looking for!

mattf

Hi:

R Connection makes an easy example using the "lattice" package.

best,

-Matt

sas = SAS Connect(); // local PC SAS

SAS Submit("

libname temp 'c:/temp';

data temp.a;

array laser (5) laser1-laser5;

do x = 1 to 25;

do i = 1 to 25;

laser(i) - ranor(12345)*ranuni(x);

end;

output;

end;

drop x i;

run;

");

dt = sas << Import Data("temp.a");

SAS Disconnect();

Rcon = R Connect();

Rcon << send(dt);

Rcon << Submit("

library(lattice);

splom(dt[c(1,2,3,4,5)], main='Laser Data')

");

plot = RConnection << Get Graphics( png );

New Window ("Laser Plot", Picture Box( plot ) );

Rcon << Disconnect();

wgoth

We actually have a sript similar to this set up with R that we currently use but we're trying to switch over a lot of our analyses into JMP to make things more accessible to the rest of our associates, but thanks!