• "Colorimeter"

    From Don Y@21:1/5 to All on Sat May 17 12:30:38 2025
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to blockedofcourse@foo.invalid on Sat May 17 12:44:53 2025
    On Sat, 17 May 2025 12:30:38 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    The people who make spectrometer-type instruments seem to be in a
    battle for ever finer resolution.

    I want a spectrometer that spans 400 to 1600 nm, or at least 800 to
    1600. I want to know if a 1310 nm laser is about 1310 and not by
    accident 1550 or something.

    I was thinking about making such an instrument. A few filters and a
    few photodiodes might work, with some overlap for interpolation.

    A rotating, graded filter and one wideband detector could work.

    Or a grating and a couple of detectors, with software to resolve
    ambiguities.

    Maybe just three detectors with different wavelength peaks.

    We did buy a couple of fiber WDM splitters, which can, for instance,
    tell us if a laser is 880 or 1300 or some such.

    Are there toy-level visual spectrometers?

    https://www.amazon.com/EISCO-Premium-Quantitative-Spectroscope-Accuracy/dp/B00B84DGDA/ref=sr_1_3?crid=21PO5QTTGGA06&dib=eyJ2IjoiMSJ9.IwA9B16820dPfj5ct0JEivvGqDD0YV5wFHFcG9c1Xss1BCoKEJvHFm_dYkhhHHK8lICo1KuioeQ85usmShFPtgMSSa0gzI2E-_
    x3ZbRTwkboNHcYYefd34pvzEKKty4RSFiiA4v0BSw_gbiEQH-khaK5lIXJ36q2q2xqW39hJj34hYp1MPTT9w4wb0RRE01F52nClp8J-VhECWQ18IWoopERU1Pl8khD8T_UPIBnauk.iFb6dsfIy8kEJvdCzNVyv8buyH2ji-Budd1i9iTh3IE&dib_tag=se&keywords=spectrometer+handheld&qid=1747511016&sprefix=
    spectrometer%2Caps%2C170&sr=8-3

    Cool. I just ordered one.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Sat May 17 22:03:07 2025
    On 17/05/2025 20:30, Don Y wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Short answer is you can't - at least without making some *very*
    questionable assumptions. It is even worse now with narrowband LEDs.

    If you are allowed to make the assumption of a radiant perfect black
    body (something that doesn't exist) then it is much easier.

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    True colorimeters were designed to match visible colours pretty much
    exactly under *any* lighting conditions (extremely tough problem). The
    first that actually worked well enough was the Imperial Match Predictor
    which ISTR was an analogue computer made in the UK by ICI strictly for
    internal use only. I don't think any documentation survives.

    There was a US made spectrometer which formed a part of it whose
    manufacturers name escapes me for the moment. Got it Hardy
    Spectrophotometer:

    https://collection.sciencemuseumgroup.org.uk/objects/co11842/ge-hardy-spectrophotometer-c-1940

    That model isn't quite the right one but it is close.

    Now any suitable paint test chart and a mobile phone will do the job.

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify the
    entire visible spectrum at ultra high resolution. Be careful though Perkin-Elmer (and others) have some very good lock out patents on this
    trick (may be about to expire).

    A few people can see longer wavelengths than most with an extra type of
    cone cell. They were sought after in WWII (pre thermal IR band imaging)
    because they could see the difference between live foliage still growing
    and cut down dying foliage used as gun emplacement camouflage.

    Denatured chlorophyll looks much darker to them.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    Measure the intensity at all wavelengths in a single shot.

    PE OES instrument in the early 1990's was the first with this.
    (I forget the model number) I was seriously impressed with it.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?B?Q2FybCBJamFtZXM=?=@21:1/5 to All on Sat May 17 20:15:42 2025
    On Sat May 17 12:44:53 2025 john larkin wrote:
    On Sat, 17 May 2025 12:30:38 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    The people who make spectrometer-type instruments seem to be in a
    battle for ever finer resolution.

    I want a spectrometer that spans 400 to 1600 nm, or at least 800 to
    1600. I want to know if a 1310 nm laser is about 1310 and not by
    accident 1550 or something.

    I was thinking about making such an instrument. A few filters and a
    few photodiodes might work, with some overlap for interpolation.

    A rotating, graded filter and one wideband detector could work.

    Or a grating and a couple of detectors, with software to resolve
    ambiguities.

    Maybe just three detectors with different wavelength peaks.

    We did buy a couple of fiber WDM splitters, which can, for instance,
    tell us if a laser is 880 or 1300 or some such.

    Are there toy-level visual spectrometers?

    https://www.amazon.com/EISCO-Premium-Quantitative-Spectroscope-Accuracy/dp/B00B84DGDA/ref=sr_1_3?crid=21PO5QTTGGA06&dib=eyJ2IjoiMSJ9.IwA9B16820dPfj5ct0JEivvGqDD0YV5wFHFcG9c1Xss1BCoKEJvHFm_dYkhhHHK8lICo1KuioeQ85usmShFPtgMSSa0gzI2E-_
    x3ZbRTwkboNHcYYefd34pvzEKKty4RSFiiA4v0BSw_gbiEQH-khaK5lIXJ36q2q2xqW39hJj34hYp1MPTT9w4wb0RRE01F52nClp8J-VhECWQ18IWoopERU1Pl8khD8T_UPIBnauk.iFb6dsfIy8kEJvdCzNVyv8buyH2ji-Budd1i9iTh3IE&dib_tag=se&keywords=spectrometer+handheld&qid=1747511016&sprefix=
    spectrometer%2Caps%2C170&sr=8-3

    Cool. I just ordered one.

    The YouTube channel Project-326 has done a couple of reviews of cheap uv-vis spectrometers. See https://www.youtube.com/watch?v=LxQmaJYMOAk for one such.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Don Y on Sat May 17 22:03:20 2025
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Spinning or oscillating prism?


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Joe Gwinn@21:1/5 to All on Sat May 17 18:42:44 2025
    On Sat, 17 May 2025 12:44:53 -0700, john larkin <jl@glen--canyon.com>
    wrote:

    On Sat, 17 May 2025 12:30:38 -0700, Don Y
    <blockedofcourse@foo.invalid> wrote:

    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    The people who make spectrometer-type instruments seem to be in a
    battle for ever finer resolution.

    I want a spectrometer that spans 400 to 1600 nm, or at least 800 to
    1600. I want to know if a 1310 nm laser is about 1310 and not by
    accident 1550 or something.

    I was thinking about making such an instrument. A few filters and a
    few photodiodes might work, with some overlap for interpolation.

    A rotating, graded filter and one wideband detector could work.

    Or a grating and a couple of detectors, with software to resolve
    ambiguities.

    Maybe just three detectors with different wavelength peaks.

    We did buy a couple of fiber WDM splitters, which can, for instance,
    tell us if a laser is 880 or 1300 or some such.

    Are there toy-level visual spectrometers?

    https://www.amazon.com/EISCO-Premium-Quantitative-Spectroscope-Accuracy/dp/B00B84DGDA/ref=sr_1_3?crid=21PO5QTTGGA06&dib=eyJ2IjoiMSJ9.IwA9B16820dPfj5ct0JEivvGqDD0YV5wFHFcG9c1Xss1BCoKEJvHFm_dYkhhHHK8lICo1KuioeQ85usmShFPtgMSSa0gzI2E-_
    x3ZbRTwkboNHcYYefd34pvzEKKty4RSFiiA4v0BSw_gbiEQH-khaK5lIXJ36q2q2xqW39hJj34hYp1MPTT9w4wb0RRE01F52nClp8J-VhECWQ18IWoopERU1Pl8khD8T_UPIBnauk.iFb6dsfIy8kEJvdCzNVyv8buyH2ji-Budd1i9iTh3IE&dib_tag=se&keywords=spectrometer+handheld&qid=1747511016&sprefix=
    spectrometer%2Caps%2C170&sr=8-3

    Cool. I just ordered one.

    In October 2022 there was a SED thread on this, "on chip
    spectrometer?".

    Joe

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From john larkin@21:1/5 to Liz Tuddenham on Sat May 17 15:44:10 2025
    On Sat, 17 May 2025 22:03:20 +0100, liz@poppyrecords.invalid.invalid
    (Liz Tuddenham) wrote:

    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Spinning or oscillating prism?

    How much spectral resolution could you get from a cell phone image?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sat May 17 19:29:54 2025
    On 5/17/2025 2:03 PM, Martin Brown wrote:
    On 17/05/2025 20:30, Don Y wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Short answer is you can't - at least without making some *very* questionable assumptions. It is even worse now with narrowband LEDs.

    If you are allowed to make the assumption of a radiant perfect black body (something that doesn't exist) then it is much easier.

    I'm not looking for a laboratory grade instrument. (hence the
    "corner cutting" caveat).

    Rather, "how does the light falling on THIS body compare to the
    light on this OTHER body" (using the same measuring instrument)

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    True colorimeters were designed to match visible colours pretty much exactly under *any* lighting conditions (extremely tough problem). The first that actually worked well enough was the Imperial Match Predictor which ISTR was an
    analogue computer made in the UK by ICI strictly for internal use only. I don't
    think any documentation survives.

    Ours controlled the color temperature of an incandescent lamp
    "seen" through a pair of filters. Then, compared the detected
    signal from the sample under test (inserted between the emitter
    and detector) in the same short time interval, looking for a
    particular color shift (analyzing blood assays)

    Again, you don't care WHAT "color" it is, just how the chemistry
    altered the color within a band of expected results.

    But, that system KNEW what to expect (expectations were dependent
    on the actual assay being run)

    There was a US made spectrometer which formed a part of it whose manufacturers
    name escapes me for the moment. Got it Hardy Spectrophotometer:

    https://collection.sciencemuseumgroup.org.uk/objects/co11842/ge-hardy-spectrophotometer-c-1940

    That model isn't quite the right one but it is close.

    Now any suitable paint test chart and a mobile phone will do the job.

    How durable are the CCDs used in phones? Especially to high intensity light sources?

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    If you are serious about doing this right then a 2D CCD sensor and a prism hires grating combo at right angles will allow you to quantify the entire visible spectrum at ultra high resolution. Be careful though Perkin-Elmer (and
    others) have some very good lock out patents on this trick (may be about to expire).

    Again, not looking to make an "instrument". The phone idea may work
    if the CCDs don't freak out with high intensity sources.

    A few people can see longer wavelengths than most with an extra type of cone cell. They were sought after in WWII (pre thermal IR band imaging) because they
    could see the difference between live foliage still growing and cut down dying
    foliage used as gun emplacement camouflage.

    Also folks who are truly colorblind. Camouflage looks different than
    natural foliage when you are just looking at the values without the
    hues to distract.

    Denatured chlorophyll looks much darker to them.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    Measure the intensity at all wavelengths in a single shot.

    Or, leverage the fact that the spectrum won't be changing in
    the short term (for some value of "short") and cycle a set
    of filters (rotating disc?) between the detector and source.

    Again, if you aren't looking for repeatability instrument to
    instrument, this may be good enough to answer the question above.

    PE OES instrument in the early 1990's was the first with this.
    (I forget the model number) I was seriously impressed with it.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Liz Tuddenham on Sat May 17 22:54:20 2025
    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter. But, probably require finer
    control (or sensing) of its current orientation.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Theo@21:1/5 to Don Y on Sun May 18 12:22:42 2025
    Don Y <blockedofcourse@foo.invalid> wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    How broad and how much resolution? There are sensors, eg: https://ams-osram.com/products/sensor-solutions/ambient-light-color-spectral-proximity-sensors

    versions of which can be found in cheap dev boards: https://shop.pimoroni.com/products/as7343-breakout?variant=41694602526803

    I'm sure I remember reading recently of a consumer grade multispectral
    camera part with a moderate resolution (something like 8x8 or 32x32) but I can't find a reference to it now. But it seems there's a phone launching
    with such a camera soon (according to rumours): https://www.gizmochina.com/2025/05/13/huawei-nova-14-series-to-launch-in-may-with-harmonyos-5-and-an-ultra-model-specs-here/

    Theo

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Sun May 18 13:37:23 2025
    On 18/05/2025 03:29, Don Y wrote:
    On 5/17/2025 2:03 PM, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify
    the entire visible spectrum at ultra high resolution. Be careful
    though Perkin-Elmer (and others) have some very good lock out patents
    on this trick (may be about to expire).

    Again, not looking to make an "instrument".  The phone idea may work
    if the CCDs don't freak out with high intensity sources.

    CCDs are almost indestructible unless you point them at the sun. Even
    then they handle it much better than a human eye. Webcams are probably a
    lot cheaper though. If you find one of the paint firm's colour matching
    apps and test chart it may already do what you want or close enough.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lasse Langwadt@21:1/5 to Martin Brown on Sun May 18 15:13:31 2025
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify the entire visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98 :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some had
    weird formats like 1024x64 pixels so I assume they were really made for spectroscopy

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From piglet@21:1/5 to Don Y on Sun May 18 12:55:37 2025
    Don Y <blockedofcourse@foo.invalid> wrote:
    On 5/17/2025 2:03 PM, Martin Brown wrote:
    On 17/05/2025 20:30, Don Y wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Short answer is you can't - at least without making some *very* questionable >> assumptions. It is even worse now with narrowband LEDs.

    If you are allowed to make the assumption of a radiant perfect black body
    (something that doesn't exist) then it is much easier.

    I'm not looking for a laboratory grade instrument. (hence the
    "corner cutting" caveat).

    Rather, "how does the light falling on THIS body compare to the
    light on this OTHER body" (using the same measuring instrument)

    I've worked with true colorimeters (dual wavelength) in the past.
    But, they were optimized to look for specific wavelengths.

    True colorimeters were designed to match visible colours pretty much exactly >> under *any* lighting conditions (extremely tough problem). The first that
    actually worked well enough was the Imperial Match Predictor which ISTR was an
    analogue computer made in the UK by ICI strictly for internal use only. I don't
    think any documentation survives.

    Ours controlled the color temperature of an incandescent lamp
    "seen" through a pair of filters. Then, compared the detected
    signal from the sample under test (inserted between the emitter
    and detector) in the same short time interval, looking for a
    particular color shift (analyzing blood assays)

    Again, you don't care WHAT "color" it is, just how the chemistry
    altered the color within a band of expected results.

    But, that system KNEW what to expect (expectations were dependent
    on the actual assay being run)

    There was a US made spectrometer which formed a part of it whose manufacturers
    name escapes me for the moment. Got it Hardy Spectrophotometer:

    https://collection.sciencemuseumgroup.org.uk/objects/co11842/ge-hardy-spectrophotometer-c-1940

    That model isn't quite the right one but it is close.

    Now any suitable paint test chart and a mobile phone will do the job.

    How durable are the CCDs used in phones? Especially to high intensity light sources?

    I calibrate the light emitted by my monitors with a device,
    but it controls the light source to do so.

    If you are serious about doing this right then a 2D CCD sensor and a prism >> hires grating combo at right angles will allow you to quantify the entire
    visible spectrum at ultra high resolution. Be careful though Perkin-Elmer (and
    others) have some very good lock out patents on this trick (may be about to >> expire).

    Again, not looking to make an "instrument". The phone idea may work
    if the CCDs don't freak out with high intensity sources.

    A few people can see longer wavelengths than most with an extra type of cone >> cell. They were sought after in WWII (pre thermal IR band imaging) because they
    could see the difference between live foliage still growing and cut down dying
    foliage used as gun emplacement camouflage.

    Also folks who are truly colorblind. Camouflage looks different than
    natural foliage when you are just looking at the values without the
    hues to distract.

    Denatured chlorophyll looks much darker to them.

    With no knowledge of the actual (visible) spectrum impinging on
    a sensor (and a bit of time to integrate results), how can I
    do this short of swapping individual filters in front of the
    sensor(s)?

    Measure the intensity at all wavelengths in a single shot.

    Or, leverage the fact that the spectrum won't be changing in
    the short term (for some value of "short") and cycle a set
    of filters (rotating disc?) between the detector and source.

    Again, if you aren't looking for repeatability instrument to
    instrument, this may be good enough to answer the question above.

    PE OES instrument in the early 1990's was the first with this.
    (I forget the model number) I was seriously impressed with it.




    If you just want to color match then your phone camera is dandy. There are
    apps used by printers and film lighting cameramen to do just that. ISTR chromlink ?


    --
    piglet

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sun May 18 12:43:58 2025
    On 5/18/2025 5:37 AM, Martin Brown wrote:
    On 18/05/2025 03:29, Don Y wrote:
    On 5/17/2025 2:03 PM, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a prism >>> hires grating combo at right angles will allow you to quantify the entire >>> visible spectrum at ultra high resolution. Be careful though Perkin-Elmer >>> (and others) have some very good lock out patents on this trick (may be
    about to expire).

    Again, not looking to make an "instrument".  The phone idea may work
    if the CCDs don't freak out with high intensity sources.

    CCDs are almost indestructible unless you point them at the sun. Even then they
    handle it much better than a human eye. Webcams are probably a lot cheaper though. If you find one of the paint firm's colour matching apps and test chart
    it may already do what you want or close enough.

    The way it was described to me (how does the light falling on this body compare to the light on some other body) suggests it was expected to receive radiant light directly (not reflected light of of two bodies that have different reflectance characteristics)

    But, I don't know how intense the light would be.

    I was asked because of my past experience with the colorimeter shining light directly onto the detector, through filters. (I've seen products that can
    tell you what color an object is, etc., using reflectance)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to piglet on Sun May 18 12:40:24 2025
    On 5/18/2025 5:55 AM, piglet wrote:
    If you just want to color match then your phone camera is dandy. There are apps used by printers and film lighting cameramen to do just that. ISTR chromlink ?

    I think the goal is to *compare* spectra (it's not my design so I'm light on details) in a manner where you can assert the differences between them.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Lasse Langwadt on Sun May 18 12:45:29 2025
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a prism >> hires grating combo at right angles will allow you to quantify the entire
    visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some had weird
    formats like 1024x64 pixels so I assume they were really made for spectroscopy

    As mentioned elsewhere, how do they fare when light is shining directly on the sensor? How do you keep it from saturating -- dark lens to attenuate the signal?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Sun May 18 22:40:33 2025
    On 18/05/2025 20:43, Don Y wrote:
    On 5/18/2025 5:37 AM, Martin Brown wrote:
    On 18/05/2025 03:29, Don Y wrote:
    On 5/17/2025 2:03 PM, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify
    the entire visible spectrum at ultra high resolution. Be careful
    though Perkin-Elmer (and others) have some very good lock out
    patents on this trick (may be about to expire).

    Again, not looking to make an "instrument".  The phone idea may work
    if the CCDs don't freak out with high intensity sources.

    CCDs are almost indestructible unless you point them at the sun. Even
    then they handle it much better than a human eye. Webcams are probably
    a lot cheaper though. If you find one of the paint firm's colour
    matching apps and test chart it may already do what you want or close
    enough.

    The way it was described to me (how does the light falling on this body compare
    to the light on some other body) suggests it was expected to receive
    radiant
    light directly (not reflected light of of two bodies that have different reflectance characteristics)

    But, I don't know how intense the light would be.

    As ever the devil is always in the details. Identical colours but with different surface finishes can look incredibly different. Vantablack is
    very much like looking into the void it is quite literally blacker than
    black!

    Any other "black" looks grey next to it.

    I was asked because of my past experience with the colorimeter shining
    light
    directly onto the detector, through filters.  (I've seen products that can tell you what color an object is, etc., using reflectance)

    You can trick almost any sensor. Human eye can be quite easily misled by didymium glass which is a narrowband Na-D blocking filter used to see
    into a bright yellow sodium flame when glassblowing.

    Side effect is to produce cartoon like out of gamut colours when the
    brain tries to compute colours from the cones. Its apparent colour
    varies radically with the source of illumination.

    The same property is shared with the natural gemstone Alexandrite.

    https://en.wikipedia.org/wiki/Chrysoberyl

    Such materials are rare and highly prized for their strange behaviour.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Don Y on Sun May 18 22:15:05 2025
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter. But, probably require finer control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an
    optical slit and a lens. Software can work out the wavelength from the rotational speed and the known characteristics of the prism. The
    resolution can be as coarse or as fine as you like and algorithms can
    work out the visual perception of line spectra (if that is what you
    need).

    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a
    steady reading (longer integration period for lower 'noise') being the
    only real differences.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Sun May 18 22:43:11 2025
    On 18/05/2025 20:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify
    the entire visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some
    had weird formats like 1024x64 pixels so I assume they were really
    made for spectroscopy

    As mentioned elsewhere, how do they fare when light is shining directly
    on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate
    the signal?

    You vary the exposure to avoid spillover.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sun May 18 19:32:41 2025
    On 5/18/2025 2:40 PM, Martin Brown wrote:
    The way it was described to me (how does the light falling on this body compare
    to the light on some other body) suggests it was expected to receive radiant >> light directly (not reflected light of of two bodies that have different
    reflectance characteristics)

    But, I don't know how intense the light would be.

    As ever the devil is always in the details. Identical colours but with different surface finishes can look incredibly different. Vantablack is very much like looking into the void it is quite literally blacker than black!

    Any other "black" looks grey next to it.

    Yeah, but reflecting light off a surface changes the problem.
    I think they are interested in characterizing the *sources*.

    I was asked because of my past experience with the colorimeter shining light >> directly onto the detector, through filters.  (I've seen products that can >> tell you what color an object is, etc., using reflectance)

    You can trick almost any sensor. Human eye can be quite easily misled by didymium glass which is a narrowband Na-D blocking filter used to see into a bright yellow sodium flame when glassblowing.

    Side effect is to produce cartoon like out of gamut colours when the brain tries to compute colours from the cones. Its apparent colour varies radically with the source of illumination.

    I am always entertained by the use of different colors to force the eye
    to focus at different distances for adjacent areas. We had a smiley face painted on the inside of an elevator door, at school, that was red/blue
    (more like orange blue). It always left riders with borderline headaches.

    The same property is shared with the natural gemstone Alexandrite.

    https://en.wikipedia.org/wiki/Chrysoberyl

    Such materials are rare and highly prized for their strange behaviour.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lasse Langwadt@21:1/5 to Don Y on Mon May 19 22:33:59 2025
    On 5/18/25 21:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a
    prism hires grating combo at right angles will allow you to quantify
    the entire visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some
    had weird formats like 1024x64 pixels so I assume they were really
    made for spectroscopy

    As mentioned elsewhere, how do they fare when light is shining directly
    on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate
    the signal?

    or a shutter to limit the time light hits the sensor

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Liz Tuddenham on Tue May 20 10:43:04 2025
    On 5/18/2025 2:15 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter. But, probably require finer
    control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an
    optical slit and a lens. Software can work out the wavelength from the rotational speed and the known characteristics of the prism. The

    Of course. But, if spinning faster than your integration interval,
    I suspect any jitter in your angular resolution might be difficult
    to factor out of the mix.

    This would, instead, suggest a slower rotation so the prism feeds
    the detector a single wavelength for a longer (continuous) period.

    That means the time to get a sampling of the spectrum is multiplied
    by the integration interval. If, instead, you could get "quick peeks"
    at each wavelength "quickly", and the more precise integration "later",
    you have more data to work with, sooner.

    [This is the approach I have historically taken with data acquisition
    as it lets me trade response time for resolution, dynamically]

    resolution can be as coarse or as fine as you like and algorithms can
    work out the visual perception of line spectra (if that is what you
    need).

    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a

    "cheerful"?

    steady reading (longer integration period for lower 'noise') being the
    only real differences.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Don Y on Wed May 21 12:05:28 2025
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/18/2025 2:15 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution >>>> and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter. But, probably require finer
    control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an optical slit and a lens. Software can work out the wavelength from the rotational speed and the known characteristics of the prism. The

    Of course. But, if spinning faster than your integration interval,
    I suspect any jitter in your angular resolution might be difficult
    to factor out of the mix.

    Mount the prism on a a flywheel and spin it rapidly. The only jitter
    might come from errors in the timing pulse (or knackered bearings!).

    One way of obtaining a jitter-free timing pulse would be to reflect a
    known pattern of light off the faces of the prism into the photocell;
    use the software to recognise it and make corrections for any long-term
    speed drift.


    This would, instead, suggest a slower rotation so the prism feeds
    the detector a single wavelength for a longer (continuous) period.

    That means the time to get a sampling of the spectrum is multiplied
    by the integration interval. If, instead, you could get "quick peeks"
    at each wavelength "quickly", and the more precise integration "later",
    you have more data to work with, sooner.

    If it spins faster you can simply integrate multiple 'passes' for as
    long as you want until the noise is negligible. The frequency response
    of the photocell and head amplifier is likely to be far wider than any mechanical system needs, so the physical narrowness of the slit and the distance from the prism will set the resolution limit. .A narrow and
    distant slit will give higher resolution at the expense of a worse S/N
    ratio, which can be overcome with a longer integration time.


    [This is the approach I have historically taken with data acquisition
    as it lets me trade response time for resolution, dynamically]

    Yes, it has many advantages.

    [...]
    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a

    "cheerful"?

    "Cheap and cheerful" is a slang [UK English] expression meaning a quick
    rough estimate or goods that aren't intended for serious long-term use.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Wed May 21 13:24:19 2025
    On 20/05/2025 18:43, Don Y wrote:
    On 5/18/2025 2:15 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution >>>>> and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter.  But, probably require finer >>> control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an
    optical slit and a lens.  Software can work out the wavelength from the
    rotational speed and the known characteristics of the prism.  The

    Of course.  But, if spinning faster than your integration interval,
    I suspect any jitter in your angular resolution might be difficult
    to factor out of the mix.

    This would, instead, suggest a slower rotation so the prism feeds
    the detector a single wavelength for a longer (continuous) period.

    I really wouldn't consider anything with moving parts. You can get
    reasonable grade replica grating for low resolution spectroscopy from
    the likes of Edmund scientific (intended for school labs).

    https://www.edmundoptics.co.uk/c/gratings/621/#27766=27766_s%3AClear%2BPolyester%2BFilm

    Or if you aren't too fussy about quality the photo filters sold to put
    rainbow stars on disco lights or on eBay. Astronomy magazines often have adverts for slightly better than average gratings for eyepieces.

    That means the time to get a sampling of the spectrum is multiplied
    by the integration interval.  If, instead, you could get "quick peeks"
    at each wavelength "quickly", and the more precise integration "later",
    you have more data to work with, sooner.

    [This is the approach I have historically taken with data acquisition
    as it lets me trade response time for resolution, dynamically]

    resolution can be as coarse or as fine as you like and algorithms can
    work out the visual perception of line spectra (if that is what you
    need).

    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a

    "cheerful"?

    UK alliterative saying.
    I guess it doesn't translate into USAian too well.

    steady reading (longer integration period for lower 'noise') being the
    only real differences.

    Figure out how much resolution you need before starting out.

    A shovelware DVD at glancing incidence can resolve the absorption lines
    in the suns spectrum if you do it just right. You look down onto the
    disk with the sun at a very shallow angle to the surface. Don't look at
    the reflection of the sun - only at the very dispersed spectrum.

    The spectrum obtained with this simple kit is impressively high
    resolution. It will also have various funny organic dye lines in with a
    modern writeable one.

    You really want aluminised media for this trick.


    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to All on Wed May 21 05:42:46 2025
    That might be better than a varied filter. But, probably require finer >>>> control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an
    optical slit and a lens. Software can work out the wavelength from the
    rotational speed and the known characteristics of the prism. The

    Of course. But, if spinning faster than your integration interval,
    I suspect any jitter in your angular resolution might be difficult
    to factor out of the mix.

    Mount the prism on a a flywheel and spin it rapidly. The only jitter
    might come from errors in the timing pulse (or knackered bearings!).

    But each wavelength (or, wavelength window) strikes the detector
    for a certain portion of time -- before the NEXT "wavelength window"
    comes around.

    You have to sample the detector's output within that window and,
    ideally, at the same time in that window as the presented wavelength
    is continuously varying *in* that window. Then, move on to the
    next "wavelength window" immediately thereafter.

    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    Without a real design, I'd be leary of making any commitments as
    to what could be achieved, there.

    By contrast, a slow spinning prism has the sampling interval determine
    the window width with each wavelength within that window seeing the
    same "exposure time".

    The drawback would be the *entire* spectrum would be sampled at a lower
    rate, corresponding to the slower rotation of the prism. You don't see
    any wavelength again until a complete "cycle" has occurred.

    One way of obtaining a jitter-free timing pulse would be to reflect a
    known pattern of light off the faces of the prism into the photocell;
    use the software to recognise it and make corrections for any long-term
    speed drift.

    If the motion is smooth and stable over a revolution (cycle) or two,
    you could likely servo the drive to maintain a frequency lock.
    Trying to adjust the sampling strobe might leave you with more
    *apparent* jitter (because you don't have infinitely fine resolution
    in time; the sampling event's motion in time looks like jitter)

    This would, instead, suggest a slower rotation so the prism feeds
    the detector a single wavelength for a longer (continuous) period.

    That means the time to get a sampling of the spectrum is multiplied
    by the integration interval. If, instead, you could get "quick peeks"
    at each wavelength "quickly", and the more precise integration "later",
    you have more data to work with, sooner.

    If it spins faster you can simply integrate multiple 'passes' for as
    long as you want until the noise is negligible. The frequency response
    of the photocell and head amplifier is likely to be far wider than any mechanical system needs, so the physical narrowness of the slit and the distance from the prism will set the resolution limit. .A narrow and
    distant slit will give higher resolution at the expense of a worse S/N
    ratio, which can be overcome with a longer integration time.

    I'll have to do some back-of-napkin figuring before I present
    the idea. And, as always, see what other pertinent details they've
    not provided. I'm not keen on being dragged into a design effort...

    [This is the approach I have historically taken with data acquisition
    as it lets me trade response time for resolution, dynamically]

    Yes, it has many advantages.

    Particularly when you *do* want data of differing qualities (and
    can leverage that to your advantage).

    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a

    "cheerful"?

    "Cheap and cheerful" is a slang [UK English] expression meaning a quick rough estimate or goods that aren't intended for serious long-term use.

    "Quick and dirty", "spit and baling wire", "bubble gum and shoe strings",
    "good enough for government work", "mickey-mouse", "jury-rigged", "jerry-built", etc.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Don Y on Wed May 21 14:19:27 2025
    Don Y <blockedofcourse@foo.invalid> wrote:

    [...]
    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to
    start with.

    Less developed software, lower sampling rate, slower ADC and less memory
    in the cheaper version. (And a garish box with "Professional" on it, to
    let customers know that this is the cheap and nasty version.)

    [...]
    "Cheap and cheerful" is a slang [UK English] expression meaning a quick rough estimate or goods that aren't intended for serious long-term use.

    "Quick and dirty", "spit and baling wire", "bubble gum and shoe strings", "good enough for government work", "mickey-mouse", "jury-rigged", "jerry-built", etc.

    That's the sort of thing. An interesting demonstration toy, rather than
    a laboratory instrument.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Martin Brown on Wed May 21 14:19:28 2025
    Martin Brown <'''newspam'''@nonad.co.uk> wrote:

    On 20/05/2025 18:43, Don Y wrote:
    On 5/18/2025 2:15 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/17/2025 2:03 PM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:


    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution >>>>> and accuracy?

    Spinning or oscillating prism?

    That might be better than a varied filter.  But, probably require finer >>> control (or sensing) of its current orientation.

    If it is spinning steadily, all you need is a synchronising pulse at
    some point once per revolution and a wide spectrum photocell with an
    optical slit and a lens.  Software can work out the wavelength from the >> rotational speed and the known characteristics of the prism.  The

    Of course.  But, if spinning faster than your integration interval,
    I suspect any jitter in your angular resolution might be difficult
    to factor out of the mix.

    This would, instead, suggest a slower rotation so the prism feeds
    the detector a single wavelength for a longer (continuous) period.

    I really wouldn't consider anything with moving parts. You can get
    reasonable grade replica grating for low resolution spectroscopy from
    the likes of Edmund scientific (intended for school labs).

    https://www.edmundoptics.co.uk/c/gratings/621/#27766=27766_s%3AClear%2BPol yester%2BFilm

    Or if you aren't too fussy about quality the photo filters sold to put rainbow stars on disco lights or on eBay. Astronomy magazines often have adverts for slightly better than average gratings for eyepieces.

    That means the time to get a sampling of the spectrum is multiplied
    by the integration interval.  If, instead, you could get "quick peeks"
    at each wavelength "quickly", and the more precise integration "later",
    you have more data to work with, sooner.

    [This is the approach I have historically taken with data acquisition
    as it lets me trade response time for resolution, dynamically]

    resolution can be as coarse or as fine as you like and algorithms can
    work out the visual perception of line spectra (if that is what you
    need).

    The same hardware could be used for an expensive high-resolution device
    or a cheap and cheerful version - the software and the time to reach a

    "cheerful"?

    UK alliterative saying.
    I guess it doesn't translate into USAian too well.

    steady reading (longer integration period for lower 'noise') being the
    only real differences.

    Figure out how much resolution you need before starting out.

    A shovelware DVD at glancing incidence can resolve the absorption lines
    in the suns spectrum if you do it just right. You look down onto the
    disk with the sun at a very shallow angle to the surface. Don't look at
    the reflection of the sun - only at the very dispersed spectrum.

    The spectrum obtained with this simple kit is impressively high
    resolution. It will also have various funny organic dye lines in with a modern writeable one.

    You really want aluminised media for this trick.

    ...or the transparent disc used to protect the end of a 'cake' of CDRs.

    If you put your nose into the hole in the middle and shut one eye, it
    displays a good spectrum.. I once had a collection of eminent people all
    sat around a table doing this at a coffee morning in the Bath Royal
    Literary and Scientific Institution.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Phil Hobbs@21:1/5 to Liz Tuddenham on Wed May 21 09:51:54 2025
    On 2025-05-21 09:19, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    [...]
    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to
    start with.

    Less developed software, lower sampling rate, slower ADC and less memory
    in the cheaper version. (And a garish box with "Professional" on it, to
    let customers know that this is the cheap and nasty version.)

    [...]
    "Cheap and cheerful" is a slang [UK English] expression meaning a quick >>> rough estimate or goods that aren't intended for serious long-term use.

    "Quick and dirty", "spit and baling wire", "bubble gum and shoe strings",
    "good enough for government work", "mickey-mouse", "jury-rigged",
    "jerry-built", etc.

    That's the sort of thing. An interesting demonstration toy, rather than
    a laboratory instrument.


    To my non-UK but Commonwealth-derived ear, "cheap and cheerful" is,
    well, more cheerful than DY's proposed equivalents.

    I'd translate it more as "dollar-store" or "chinesium".

    Cheers

    Phil Hobbs

    --
    Dr Philip C D Hobbs
    Principal Consultant
    ElectroOptical Innovations LLC / Hobbs ElectroOptics
    Optics, Electro-optics, Photonics, Analog Electronics
    Briarcliff Manor NY 10510

    http://electrooptical.net
    http://hobbs-eo.com

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Liz Tuddenham on Thu May 22 09:49:14 2025
    On 5/21/2025 6:19 AM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to
    start with.

    Are you expecting to frequently sample the entire spectrum in each
    "pass" ("revolution")? Or, walk the sampling window up/down the spectrum
    in stages?

    I.e., how much time are you expecting to spend PROCESSING the sampled
    data vs. acquiring more data?

    Less developed software, lower sampling rate, slower ADC and less memory
    in the cheaper version. (And a garish box with "Professional" on it, to
    let customers know that this is the cheap and nasty version.)

    [...]
    "Cheap and cheerful" is a slang [UK English] expression meaning a quick >>> rough estimate or goods that aren't intended for serious long-term use.

    "Quick and dirty", "spit and baling wire", "bubble gum and shoe strings",
    "good enough for government work", "mickey-mouse", "jury-rigged",
    "jerry-built", etc.

    That's the sort of thing. An interesting demonstration toy, rather than
    a laboratory instrument.

    None of the above imply a "toy". Rather, just not spending much
    resources trying to dot every I and cross every T.

    E.g., as presented to me, there was no need for calibration against
    a reference standard, "flat" response across the spectrum, etc.

    A "laboratory grade" device likely WOULD impose such specifications.
    And, bear an associated (likely high) cost.

    E.g., one of the activities at one of my "summer jobs" (college) was
    in testing hand tools. Which ISO standard defines the specifications
    for a "hammer" (WHICH type of hammer?)? How can you get the specifications
    of a particular "hammer" so that you can compare model A to model B, manufacturer X to manufacturer Y?

    Yet, you know that "hammers" have to be tested -- if only to ensure the "process" isn't deviating from expected norms.

    And, once you have devised a suitable test (in whatever bogounits seem appropriate), you can then sample your competitors' wares to see
    how you stand up.

    None of this being of direct interest to the consumer as the units are
    likely not anything that the consumer can relate to directly. It can,
    however, tell you how much you can improve or cost-cut your product
    (and process) without risking your product looking inferior to those
    of your competitors.

    This is far more common than "laboratory type specifications" in many industries. (as engineers, we often fixate on numbers that have little practical meaning)

    How *hard* should the aspirins you take be? Would a larger/thinner dosing
    form be "better" -- for the consumer, absorption, manufacture? "Gee,
    why is this pill so much smaller yet claims to be the same STRENGTH as
    the larger/heavier ones I was taking?"

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Theo on Thu May 22 10:34:30 2025
    On 5/18/2025 4:22 AM, Theo wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general? Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    How broad and how much resolution?

    I've not been read into those details. It's unclear if they are *known*
    or being withheld (as they know I'm not interested in any more work; why disclose information that you don't have to?)

    There are sensors, eg: https://ams-osram.com/products/sensor-solutions/ambient-light-color-spectral-proximity-sensors

    Thanks, I will pass that along.

    versions of which can be found in cheap dev boards: https://shop.pimoroni.com/products/as7343-breakout?variant=41694602526803

    I'm sure I remember reading recently of a consumer grade multispectral
    camera part with a moderate resolution (something like 8x8 or 32x32) but I can't find a reference to it now. But it seems there's a phone launching with such a camera soon (according to rumours): https://www.gizmochina.com/2025/05/13/huawei-nova-14-series-to-launch-in-may-with-harmonyos-5-and-an-ultra-model-specs-here/

    That would target a different application (IMO). As presented to me, they're just looking for characterizing the light falling on a *spot*. If
    different (e.g., bandwidth sensitive) detectors were employed AT that
    spot, I would assume they would have to be treated as a single point
    (despite there being some obvious separations involved in their manufacture)

    I.e., almost like a photographer's "light meter" but with the interest
    being on the spectral content and not the overall intensity.

    [Whether this is true or not, it has influenced how *I* have thought
    about the problem -- in terms of function, size, portability, power requirements, etc. Assumptions are always the bane of a good design... :< ]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Thu May 22 19:45:01 2025
    On 22/05/2025 18:34, Don Y wrote:
    On 5/18/2025 4:22 AM, Theo wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:
    Not quite, but, close enough...

    How can I determine the spectrum of incident light on a sensor,
    in general?  Then, how many corners can I cut to sacrifice resolution
    and accuracy?

    How broad and how much resolution?

    I've not been read into those details.  It's unclear if they are *known*
    or being withheld (as they know I'm not interested in any more work; why disclose information that you don't have to?)

     There are sensors, eg:
    https://ams-osram.com/products/sensor-solutions/ambient-light-color-spectral-proximity-sensors

    Thanks, I will pass that along.

    versions of which can be found in cheap dev boards:
    https://shop.pimoroni.com/products/as7343-breakout?variant=41694602526803

    I'm sure I remember reading recently of a consumer grade multispectral
    camera part with a moderate resolution (something like 8x8 or 32x32)
    but I
    can't find a reference to it now.  But it seems there's a phone launching >> with such a camera soon (according to rumours):
    https://www.gizmochina.com/2025/05/13/huawei-nova-14-series-to-launch-in-may-with-harmonyos-5-and-an-ultra-model-specs-here/

    That would target a different application (IMO).  As presented to me, they're
    just looking for characterizing the light falling on a *spot*.  If
    different (e.g., bandwidth sensitive) detectors were employed AT that
    spot, I would assume they would have to be treated as a single point
    (despite there being some obvious separations involved in their
    manufacture)

    I.e., almost like a photographer's "light meter" but with the interest
    being on the spectral content and not the overall intensity.

    [Whether this is true or not, it has influenced how *I* have thought
    about the problem -- in terms of function, size, portability, power requirements, etc.  Assumptions are always the bane of a good design...
    :< ]
    If the light levels are very high then you can get LEDs with emission
    profiles of about 50nm width. They work as sensors in the opposite
    direction with some leakage for higher energy photons. Choose them
    wisely and calibrate against a reference white and you might have
    something that is both cheap accurate and durable.


    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Liz Tuddenham@21:1/5 to Don Y on Fri May 23 10:04:06 2025
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/21/2025 6:19 AM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to start with.

    Are you expecting to frequently sample the entire spectrum in each
    "pass" ("revolution")? Or, walk the sampling window up/down the spectrum
    in stages?

    I was expecting to sweep the whole spectrum at high speed many times,
    then analyse the captured data. Television-type technology could easily
    cope with that data rate from a single photocell.

    I.e., how much time are you expecting to spend PROCESSING the sampled
    data vs. acquiring more data?

    The ratio can be varied by either the user or the designer of the
    instrument. If greater accuracy is required, it will take longer to do
    both the capture and the analysis.

    [...]

    E.g., as presented to me, there was no need for calibration against
    a reference standard, "flat" response across the spectrum, etc.

    A "laboratory grade" device likely WOULD impose such specifications.
    And, bear an associated (likely high) cost.

    Some sort of reference source could be used to generate a known spectrum
    every 'n' passes; this would also serve for synchronising purposes.
    There would be no need to accurately control the rotational speed as
    long as it was steady in the short term. The reference spectrum would calibrate the span and the end points; it could also calibrate the
    spectral amplitude response of the photo-detector.

    A small gas-filled discharge tube, pulsed by an ignition transformer,
    would suffice for non-critical calibration.


    --
    ~ Liz Tuddenham ~
    (Remove the ".invalid"s and add ".co.uk" to reply)
    www.poppyrecords.co.uk

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Liz Tuddenham on Fri May 23 13:10:41 2025
    On 23/05/2025 10:04, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    On 5/21/2025 6:19 AM, Liz Tuddenham wrote:
    Don Y <blockedofcourse@foo.invalid> wrote:

    Sampling jitter within a window corresponds to spectral resolution;
    the more jitter, the wider the range of wavelengths potentially
    involved in the sample (over time). As sampling the detector
    is a discrete time event (the interval between samples being the
    width of the window), how frequently you do this further defines
    the spectral resolution.

    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to
    start with.

    Are you expecting to frequently sample the entire spectrum in each
    "pass" ("revolution")? Or, walk the sampling window up/down the spectrum
    in stages?

    I was expecting to sweep the whole spectrum at high speed many times,
    then analyse the captured data. Television-type technology could easily
    cope with that data rate from a single photocell.

    That was how the early Hardy spectrophotometers did it back in the day
    when photomultiplier tubes were large rare expensive beasts surrounded
    by insanely high voltages and lots of precision megohm resistors.

    I still have a few small mirror bits from taking one apart long ago.

    Today with ultra cheap LCDs and some with piezo shift facility the trend
    is towards making a 2D spectrum on a standard rectangular CCD sensor
    with high dispersion on one axis from a grating and low dispersion in
    the other from a prism. Mapping the entire spectrum into a 2D pattern.

    Echelle spectrograph is the keyword you want. Oxford instruments make
    rather high end ones but you don't need anything so fancy for this.

    https://andor.oxinst.com/learning/view/article/echelle-spectrographs-a-flexible-tool-for-spectroscopy

    Solar spectrum measured conventionaly but displayed in that style
    because it allows it to fit more easily on a page here:

    https://noirlab.edu/public/images/noao-sun/



    A small gas-filled discharge tube, pulsed by an ignition transformer,
    would suffice for non-critical calibration.

    A neon lamp or a mercury vapour one will do for a wavelength reference.
    It's hard to get a sodium lamp small enough and at a good price.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Liz Tuddenham on Sat May 24 05:42:46 2025
    On 5/23/2025 2:04 AM, Liz Tuddenham wrote:
    I was assuming very fast sampling so that the presentation of each line
    was captured by many samples, that way the software could sort it out
    over a large number of repeated passes. Keep the hardware simple and
    let the software deal with the errors if it can be given enough data to
    start with.

    Are you expecting to frequently sample the entire spectrum in each
    "pass" ("revolution")? Or, walk the sampling window up/down the spectrum
    in stages?

    I was expecting to sweep the whole spectrum at high speed many times,
    then analyse the captured data. Television-type technology could easily
    cope with that data rate from a single photocell.

    I was looking at the opposite approach; continuously reducing data
    to keep memory and processing requirements modest -- no idea what
    OTHER things a processor would be taxed with doing WHILE gathering
    this data.

    I.e., how much time are you expecting to spend PROCESSING the sampled
    data vs. acquiring more data?

    The ratio can be varied by either the user or the designer of the
    instrument. If greater accuracy is required, it will take longer to do
    both the capture and the analysis.

    [...]

    E.g., as presented to me, there was no need for calibration against
    a reference standard, "flat" response across the spectrum, etc.

    A "laboratory grade" device likely WOULD impose such specifications.
    And, bear an associated (likely high) cost.

    Some sort of reference source could be used to generate a known spectrum every 'n' passes; this would also serve for synchronising purposes.

    If you, instead, just interpret some "local" source as a reference,
    then all you need to do is compare your current data to that reference.
    As long as your detector's response doesn't drift faster than your
    exposure to new "references", the user never sees the issue of
    "calibration".

    E.g., I designed a sensor array that monitored for the presence of
    samples and reagents in some 60 different locations, concurrently.
    The *process* could be exploited to give the software the upper
    hand on making deductions so the hardware could be dirt cheap
    (there was a -50% +300% tolerance from sensor to sensor -- BUT,
    there were times when you could KNOW that certain sensors were
    "seeing nothing" so X on sensor 1 and Y on sensor 2 each represented
    the same state, regardless of that inherent manufacturing tolerance)

    Throughout my career, I've eschewed "calibration" as a costly
    additional option that doesn't usually add value to a "process".

    E.g., when tablets are formed, you can only monitor the forces
    exerted on them as a variable amount of material is compressed to
    a fixed geometry; or, the resulting size as a fixed force is
    exerted.

    But, most solid dosing forms don't care about forces or dimensions
    of individual doses. Instead, they are concerned with the actual
    MASS of the material that "happened" to be present for the event.
    Yet, you can't WEIGH to a submilligram precision individual
    items at a sample rate of hundreds per second! (but, you CAN
    measure sizes or forces).

    So, you create a product specific profile of force vs. mass (or,
    size vs. mass, depending on manufacturing technology used).
    And, set control limits based on bogo-units (you only care
    what those actual forces/sizes are if you want to have process
    constraints that are portable from machine to machine -- and,
    you don't typically care about that!)

    Want to be able to claim NBS traceability for your measurements?
    OK, but does that improve the quality of your product? Or,
    just make you feel like you're more sophisticated?

    There would be no need to accurately control the rotational speed as
    long as it was steady in the short term. The reference spectrum would calibrate the span and the end points; it could also calibrate the
    spectral amplitude response of the photo-detector.

    A small gas-filled discharge tube, pulsed by an ignition transformer,
    would suffice for non-critical calibration.

    As would the "flashlight" in the phone the user happened to have in
    his pocket, at the time.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sat May 24 05:26:57 2025
    On 5/22/2025 11:45 AM, Martin Brown wrote:
    On 22/05/2025 18:34, Don Y wrote:

    I.e., almost like a photographer's "light meter" but with the interest
    being on the spectral content and not the overall intensity.

    [Whether this is true or not, it has influenced how *I* have thought
    about the problem -- in terms of function, size, portability, power
    requirements, etc.  Assumptions are always the bane of a good design... :< ]
    If the light levels are very high then you can get LEDs with emission profiles
    of about 50nm width. They work as sensors in the opposite direction with some leakage for higher energy photons. Choose them wisely and calibrate against a reference white and you might have something that is both cheap accurate and durable.

    My original approach was along similar lines. But, resulted in a large-ish sensor (many LEDs). I had toyed with a similar "sun detector" concept
    (LEDs focused in different directions along a hemisphere) many months back.

    Again, without specifics, I didn't know how much leeway I could propose in
    a solution. So, went looking for smaller, more "integrated", that they
    could have more flexibility in adapting, packaging, etc.

    [I'm not keen on spending a lot of time on this as it's just a "favor"
    for an old client (who treated me quite we$$). Hopefully, they can sort
    out specifics that are more appropriate to their design constraints. I
    also want to avoid the possibility of getting "sucked into" a design;
    I've got far too much on my plate, already, than to have to deal with
    a client! :< ]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sat May 24 06:24:29 2025
    On 5/18/2025 2:43 PM, Martin Brown wrote:
    On 18/05/2025 20:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a prism >>>> hires grating combo at right angles will allow you to quantify the entire >>>> visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some had >>> weird formats like 1024x64 pixels so I assume they were really made for
    spectroscopy

    As mentioned elsewhere, how do they fare when light is shining directly on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate the >> signal?

    You vary the exposure to avoid spillover.

    You can only use an electronic shutter to a limited degree. You still
    have to worry about protecting the sensor from being "cooked". I.e.,
    a mechanical shutter (something best purchased as silly to try to design)

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Lasse Langwadt on Sat May 24 13:07:59 2025
    On 5/19/2025 1:33 PM, Lasse Langwadt wrote:
    On 5/18/25 21:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and a prism >>>> hires grating combo at right angles will allow you to quantify the entire >>>> visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some had >>> weird formats like 1024x64 pixels so I assume they were really made for
    spectroscopy

    As mentioned elsewhere, how do they fare when light is shining directly on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate the >> signal?

    or a shutter to limit the time light hits the sensor

    There's still a limit as to the peak intensity that a sensor can
    tolerate. And, gating the light (instead of attenuating it)
    means there is no signal when the source is gated off.

    Fine if you are making a device with a button that says "measure now".
    But, if you expect to be able to collect data at any time, you
    want to be sure data is available.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Martin Brown@21:1/5 to Don Y on Sun May 25 10:07:53 2025
    On 24/05/2025 21:07, Don Y wrote:
    On 5/19/2025 1:33 PM, Lasse Langwadt wrote:
    On 5/18/25 21:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and
    a prism hires grating combo at right angles will allow you to
    quantify the entire visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence, some
    had weird formats like 1024x64 pixels so I assume they were really
    made for spectroscopy

    As mentioned elsewhere, how do they fare when light is shining
    directly on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate
    the signal?

    or a shutter to limit the time light hits the sensor

    There's still a limit as to the peak intensity that a sensor can
    tolerate.  And, gating the light (instead of attenuating it)
    means there is no signal when the source is gated off.

    Simplest solution is to limit the aperture that you let the light in
    through which is normally focussed onto a narrow slit anyway. You might
    get a bit of an issue with readout smearing but it probably won't be too
    bad.

    Please bear in mind that my experience with spectroscopy the problem was
    mostly getting enough light to have *any* signal to noise.

    Fine if you are making a device with a button that says "measure now".
    But, if you expect to be able to collect data at any time, you
    want to be sure data is available.

    In extremis the measure now button could just move a spring loaded
    mechanical shutter that normally blocks the light path.

    Unless the thing is imaging a nuclear blast, steel furnace or an arc
    lamp then I don't think light intensity is likely to harm a modern CCD.
    There are hot mirror and anti-UV low pass filters to protect such
    equipment from hostile radiation.

    --
    Martin Brown

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Don Y@21:1/5 to Martin Brown on Sun May 25 11:08:37 2025
    On 5/25/2025 2:07 AM, Martin Brown wrote:
    As mentioned elsewhere, how do they fare when light is shining directly on the
    sensor?  How do you keep it from saturating -- dark lens to attenuate the >>>> signal?

    or a shutter to limit the time light hits the sensor

    There's still a limit as to the peak intensity that a sensor can
    tolerate.  And, gating the light (instead of attenuating it)
    means there is no signal when the source is gated off.

    Simplest solution is to limit the aperture that you let the light in through which is normally focussed onto a narrow slit anyway. You might get a bit of an
    issue with readout smearing but it probably won't be too bad.

    The issue would be knowing WHEN that was necessary and when it would
    suppress the signal. You'd have to leave it "clamped down", normally,
    take a reading and then decide if, instead, you should have "opened
    it up".

    And, once having made that decision, hope that conditions don't change.

    Please bear in mind that my experience with spectroscopy the problem was mostly
    getting enough light to have *any* signal to noise.

    I think their application is looking *into* light sources. The way the
    problem was presented, it was measuring light falling here vs. there vs...

    Fine if you are making a device with a button that says "measure now".
    But, if you expect to be able to collect data at any time, you
    want to be sure data is available.

    In extremis the measure now button could just move a spring loaded mechanical shutter that normally blocks the light path.

    That assumes there is a definite time to make a measurement. Most of the systems that I've designed act continuously; the user isn't constrained to follow a set process -- A, then B, then C.

    So, typically, a service is just providing updates to a variable that process(es) can examine at their leisure (you mmap() the hardware device
    as if a simple datum instead of calling a procedure to make the measurement)

    Consider, you don't ask a UART to fetch a character for you to consume.
    Ditto a network stack. Or, a set of digital I/Os. Or, temperature
    sensors, etc.

    Instead, you consume what has already been *discovered* and react accordingly. ("Oh, my! The access panel has been opened, unexpectedly! How do I handle this event?")

    I.e., unlike a laboratory device that requires a particular set of actions
    to yield results, the device provides data and you have to sort out what
    the user is likely doing.

    Unless the thing is imaging a nuclear blast, steel furnace or an arc lamp then
    I don't think light intensity is likely to harm a modern CCD. There are hot mirror and anti-UV low pass filters to protect such equipment from hostile radiation.


    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lasse Langwadt@21:1/5 to Martin Brown on Thu May 29 01:11:20 2025
    On 5/25/25 11:07, Martin Brown wrote:
    On 24/05/2025 21:07, Don Y wrote:
    On 5/19/2025 1:33 PM, Lasse Langwadt wrote:
    On 5/18/25 21:45, Don Y wrote:
    On 5/18/2025 6:13 AM, Lasse Langwadt wrote:
    On 5/17/25 23:03, Martin Brown wrote:

    If you are serious about doing this right then a 2D CCD sensor and >>>>>> a prism hires grating combo at right angles will allow you to
    quantify the entire visible spectrum at ultra high resolution.

    use a CD https://youtu.be/EoAZ-u6hn6g?si=Mv-DfJ5swtq2-j1X&t=98  :)

    eons ago we used some CCDs as detectors for X-ray fluorescence,
    some had weird formats like 1024x64 pixels so I assume they were
    really made for spectroscopy

    As mentioned elsewhere, how do they fare when light is shining
    directly on the
    sensor?  How do you keep it from saturating -- dark lens to
    attenuate the signal?

    or a shutter to limit the time light hits the sensor

    There's still a limit as to the peak intensity that a sensor can
    tolerate.  And, gating the light (instead of attenuating it)
    means there is no signal when the source is gated off.

    Simplest solution is to limit the aperture that you let the light in
    through which is normally focussed onto a narrow slit anyway. You might
    get a bit of an issue with readout smearing but it probably won't be too
    bad.

    Please bear in mind that my experience with spectroscopy the problem was mostly getting enough light to have *any* signal to noise.

    Fine if you are making a device with a button that says "measure now".
    But, if you expect to be able to collect data at any time, you
    want to be sure data is available.

    In extremis the measure now button could just move a spring loaded
    mechanical shutter that normally blocks the light path.

    Unless the thing is imaging a nuclear blast, steel furnace or an arc
    lamp then I don't think light intensity is likely to harm a modern CCD.
    There are hot mirror and anti-UV low pass filters to protect such
    equipment from hostile radiation.


    https://www.reddit.com/r/Volvo/comments/1ke98nv/never_film_the_new_ex90_because_you_will_break/?embed_host_url=https%3A%2F%2Fwww.thedrive.com%2Fnews%2Fvolvo-ex90s-lidar-sensor-will-fry-your-phones-camera

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)