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; } } }

Enhanced Log - n added after "column name"

terapin

Folks,

In utilizing the Enhanced log with data tables that have long, descriptive column names, the output is placing a "n" after the variable name as shown in some examples below. Normally, the "n" isn't produced when the column name is short and doesn't include non-alphabetical characters such as & or ,. While the Enhanced Log code will run with these additional characters, I'd like to better understand why the "n" is produced and whether I should keep them as part of my code or remove them?

// Select where
Data Table( "PESD Stationary, Envidas SQL Data Table, 1-Min" ) <<
Select where( :"Ambient NOx, N500 Status"n == 31 );


// Subset data table
Data Table( "PESD Stationary, Envidas SQL Data Table, 1-Min" ) << Subset(
	Selected Rows( 1 ),
	columns(
		:"Date & Time"n, :Date, :Day of Year, :"Ambient NO, N500 (ppb)"n,
		:"Ambient NO, N500 Status"n, :"Ambient NO2, N500 (ppb)"n,
		:"Ambient NO2, N500 Status"n, :"Ambient NOx, N500 (ppb)"n,
		:"Ambient NOx, N500 Status"n
	)
);

Accepted answers

jthi

In addition to txnelson's explanation, here is one link related to "col name"n syntax as you might see Name() syntax in older scripts Deprecating the Name() parser directive in JMP 16 and JMP Help - Scripting Guide - Names

All comments

txnelson

The "xxxxxxx"n version of the column name is produced when JMP determines that if the actual column name will not parse correctly in open code. The easiest way to demonstrate this, is with the following example.

If a variable is named "X-Y" and one wants to create a new variable using that column, and with it, add it to the variable Z, the JSL would be

newVar = X - Y + Z;

JMP would be looking for a variable named X, a variable named Y and a variable named Z. Basically, JMP would get confused.

newVar = "X - Y"n + Z;

clarifies the situation.

terapin

Not sure I completely understand given that I'm scoping my column names such as :"Column Name, Column Units". With the column scoping ( : ) I would think JMP wouldn't get confused whether I was working with a variable vs a column name.

txnelson

JMP does not know how you are going to use the column names. So it is playing it safe, in that when it comes across a column name that "could" be confusing, it converts to the :xxxxxxx"n format. And in turn, it is wise for you to use it when you see that it might be confusing, even if is some cases, you might get away without a problem.

jthi