"bracketing" or "clipping" -- input needed on correct terminology

[Jeffrey Warren]

Hi, all - I'm planning to add a long-needed feature where you can indicate a range of wavelengths to "clip" your spectrum to -- i.e. display only 400-800 nm. 

This is nice just for looking at spectra without all the above-and-below-range data which is probably useless anyways. But it's also really key for things like doing analysis on fluorescence spectra, because we can clip out the region where the laser light hits, as in the image below. 

What is this really called in the lab? "bracketing"? "clipping"? I want to name it with a good convention in the code, from the start. 

Thanks!

Jeff

[Robert Dyer]

Clipping makes me think "amplitude". How about "set bandwidth" like in any filter?

 

---

From: "Jeffrey Warren" <je...@publiclab.org>
Sent: Monday, July 20, 2015 10:02 AM

--
Post to this group at plots-sp...@googlegroups.com
 
Public Lab mailing lists (http://publiclab.org/lists) are great for discussion, but to get attribution, open source your work, and make it easy for others to find and cite your contributions, please publish your work at http://publiclab.org
---
You received this message because you are subscribed to the Google Groups "plots-spectrometry" group.
To unsubscribe from this group and stop receiving emails from it, send an email to plots-spectrome...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
 

[Jeffrey Warren]

Oh, good call on clipping -- we already use that for exactly what you mention -- when amplitude is too high. Words!

Bandwidth is good - does that sound ambiguous to folks since it's so broadly used for internet speed? Like, imagine a button that says:

[ Set spectrum bandwidth ]

or maybe

[ Set spectrum range ]

[Yagiz Sutcu]

I am not sure about out of 400-800 nm range is useless statement but having this feature sounds good. And it is basically zooming on x axis. I do not think it has a name though. Range selection is self-explanatory and simple enough for anyone.

Yagiz

[Jeffrey Warren]

So maybe [Select wavelength range] ?

Sorry, i didn't mean it's useless -- i mean that for a given use, or a given device you've built, you might decide that that's all you need, or for a certain scenario it's useless. Also, the data would still be there -- it'd just set a default display range. 

[Yagiz Sutcu]

That sounds good to me! And thanks for this feature Jeff, that would be useful to see small differences between spectral data more easily!

[Jeffrey Warren]

:-)

you can follow my progress a bit on this gigantic issue checklist: https://github.com/publiclab/spectral-workbench/pull/139