Creating a box plot

Hi,

I would use Extract to create subsets of the waves where you have a label. A caveat is a null str will return a NaN, we can test for that with numtype and 2 being a NaN.

Extract unit4, unit4_sub, numtype(strlen(Unit4))!=2

Extract modeled_kT_DPB4, modeled_kT_DPB4_sub, numtype(strlen(Unit4))!=2

Create the box and whisker on the "sub" waves

Andy

Hi Andy,

When I do this and create a box plot I am still only getting 1 box that combines all of my modeled_kT data. How do I split it up to individual boxes based on Unit?

You'll want to make a multi-column wave for your data, so that each unit has its own column. That way each Unit column will become its own category in the plot

Hi,

Worked the problem a bit and wrote a little function.

It takes three inputs, the text wave with labels, the wave with the data, and a flag on what to do with labels that are empty,"", keep them as "Other" or ignore them.  It creates/uses a directory called "box" with the data waves and a corresponding label wave. In the dialog box select the data waves as waves to plot and the unique labels as the x wave.

Andy

Thanks so much! I had to edit a little to save the data into a different folder but otherwise seems to work well. I really appreciate the help!

Kind of as a follow up to this...I am wanting to also calculate the lognormal mean of my data for each new DW. They seem to have a  lognormal distribution so I am using the attached equation. 

I am first creating a table...

Make/O/N=(numnts(uniquelabels)) MLEMean

Then trying to populate my table with this mean values by 

MLEMean[0]=1/numpnts(DW_1)*sum(ln(DW_1))

MLEMean[1]=1/numpnts(DW_2)*sum(ln(DW_2))

MLEMean[2]=1/numpnts(DW_3)*sum(ln(DW_3))

Etc...

However, Igor doesn't like that I have a function and not a wave variable within the sum brackets. Any good way around this?

Thanks!

The error is because the ln function expects a number, but if you put that expression in a wave assignment, each point in the wave will get passed to the ln function. You could do something like this:

and then call:

Yeah, the sum() function requires a wave, not a number returned from a function.

The MatrixOP operation offers (in this case) a more natural way to do this. Here is an example:

The peculiarity here is the "term1" is a one-point wave, not a variable. But it's easy to handle that. And MatrixOP is all about functions being applied to waves and returning waves. As the name implies, it is more oriented toward matrices; and that's why you need "sumcols" and not just "sum". You are working with a one-column matrix here :)

Ok, that makes sense. thank you! 

And my colleague AG here has pointed out that you can replace that expression with this:

lnWave needs to be the same length as the input wave dw, methinks: