<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en" xmlns="http://www.w3.org/2005/Atom"><title>Recent changes to feature-requests</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/" rel="alternate"/><link href="https://sourceforge.net/p/beamprofiler/feature-requests/feed.atom" rel="self"/><id>https://sourceforge.net/p/beamprofiler/feature-requests/</id><updated>2024-12-22T16:01:34.410000Z</updated><subtitle>Recent changes to feature-requests</subtitle><entry><title>#6 Output gaussian fit peak position</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/6/?limit=25#3253" rel="alternate"/><published>2024-12-22T16:01:34.410000Z</published><updated>2024-12-22T16:01:34.410000Z</updated><author><name>Wenjamin Rosenfeld</name><uri>https://sourceforge.net/u/wenjarose/</uri></author><id>https://sourceforge.net6968500375ba1799e2dd0b357011c07b0574a9b5</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Dear Peter,&lt;br/&gt;
for trying this out, I have implemented the output of fit x0 into the header of the 1D plot profile windows. It  will be released in the 1.4.2 version.&lt;/p&gt;
&lt;p&gt;Best&lt;br/&gt;
Wenjamin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#8 Highlight Saturated Pixels</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/8/?limit=25#5e5a" rel="alternate"/><published>2024-12-21T15:57:10.411000Z</published><updated>2024-12-21T15:57:10.411000Z</updated><author><name>Wenjamin Rosenfeld</name><uri>https://sourceforge.net/u/wenjarose/</uri></author><id>https://sourceforge.netd3d7b1bae7e0b4cfec472b6ec224a6d8f4697091</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</summary></entry><entry><title>#8 Highlight Saturated Pixels</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/8/?limit=25#1c79" rel="alternate"/><published>2024-12-16T14:19:32.159000Z</published><updated>2024-12-16T14:19:32.159000Z</updated><author><name>David Demmer</name><uri>https://sourceforge.net/u/drmdemmer/</uri></author><id>https://sourceforge.net424295913d8d655ef87994bc85c4dd0a1c2e236f</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Apologies. I completely failed to RTFM. Thanks again for an excellent tool.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#5 Implementation of Laguerre-Gaussian beams</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/5/?limit=25#88c8/6fe1/e2b3" rel="alternate"/><published>2024-12-15T14:23:26.540000Z</published><updated>2024-12-15T14:23:26.540000Z</updated><author><name>Wenjamin Rosenfeld</name><uri>https://sourceforge.net/u/wenjarose/</uri></author><id>https://sourceforge.netf96a820b582311f629523bb874fa5c2033038cc3</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Hi David, &lt;br/&gt;
thank you for the image, the profile looks cool inded!&lt;br/&gt;
Best&lt;br/&gt;
Wenjamin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#8 Highlight Saturated Pixels</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/8/?limit=25#25dd" rel="alternate"/><published>2024-12-15T14:15:15.190000Z</published><updated>2024-12-15T14:15:15.190000Z</updated><author><name>Wenjamin Rosenfeld</name><uri>https://sourceforge.net/u/wenjarose/</uri></author><id>https://sourceforge.net8b4154960963930466b38f3b81d4494675739538</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Dear David,&lt;br/&gt;
thank you for bringing this up. This feature already exists - all you need to do is to install the provided LUT OBP_gray_sat.lut as described in the instructions. When you set  it in the Lookup Table selector it will do exactly what you wish - provide a linear grayscale with the 255 pixels being shown in red.&lt;/p&gt;
&lt;p&gt;Best regards&lt;br/&gt;
Wenjamin&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Highlight Saturated Pixels</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/8/" rel="alternate"/><published>2024-12-09T01:00:15.145000Z</published><updated>2024-12-09T01:00:15.145000Z</updated><author><name>David Demmer</name><uri>https://sourceforge.net/u/drmdemmer/</uri></author><id>https://sourceforge.net231ba2e1983f789b786749ff9e17a4a0fad1602e</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I find that inexperienced users frequently try to use images where some pixels are saturated. Many years ago I used a Spiricon beam profiler that had the handy feature that any pixel with intensity of 255 was coloured red when viewing a grey-scale image. This made it super easy to ensure the attenuation was set correctly even when the monitor was set up on the other side of  the optical table.&lt;/p&gt;
&lt;p&gt;I was hoping you might consider implementing something like that. Maybe a "Highlight Saturated Pixels" option?&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Highlight Saturated Pixels</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/8/" rel="alternate"/><published>2024-12-09T01:00:15.145000Z</published><updated>2024-12-09T01:00:15.145000Z</updated><author><name>David Demmer</name><uri>https://sourceforge.net/u/drmdemmer/</uri></author><id>https://sourceforge.netd62d9e99746fba8bdb400912bca416c3c79d7418</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 8 has been modified: Highlight Saturated Pixels&lt;br/&gt;
Edited By: Wenjamin Rosenfeld (wenjarose)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'closed'&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#5 Implementation of Laguerre-Gaussian beams</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/5/?limit=25#88c8/6fe1" rel="alternate"/><published>2024-12-09T00:52:01.576000Z</published><updated>2024-12-09T00:52:01.576000Z</updated><author><name>David Demmer</name><uri>https://sourceforge.net/u/drmdemmer/</uri></author><id>https://sourceforge.net28d57f760f34bf37eb3367e906d5d8c60ced3447</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;I was just browsing this thread and saw your request for an LG image. Here's one I took a while back. It's likely a combination of LG00 and LG05. I obtained it by deliberately misaligning the pump beam into an Nd:YAG NPRO laser. Sorry about the poor quality. Not much good for anything other than "looks cool" I'm afraid.&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>#6 Output gaussian fit peak position</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/6/?limit=25#62b5" rel="alternate"/><published>2024-07-22T19:22:51.578000Z</published><updated>2024-07-22T19:22:51.578000Z</updated><author><name>Wenjamin Rosenfeld</name><uri>https://sourceforge.net/u/wenjarose/</uri></author><id>https://sourceforge.net4b59cde27923a5771d70f9b14023862312a5d0d1</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Dear Peter,&lt;br/&gt;
thank you for your feedback!&lt;/p&gt;
&lt;p&gt;As a matter of clarification: the fit center positions of the 1D profiles were not output because they are given in "profile coordinates", i.e. along the cuts and thus change when the axes rotate. One can associate them with x and y only when the axis angle is fixed to 0°. In all other cases I am not so sure how meaningful these numbers are. Of course it is not difficult to output them (visible in the header of the profile plot), I just would like to avoid confusing users with numbers whose meaning is unclear.&lt;br/&gt;
Regarding pointing metrics - this is indeed an interesting question. A fit definitely copes better with (uniform) background level variations, on the other hand the 2D COM-based metrics take into account many more pixels and thus may give a better average.&lt;/p&gt;
&lt;p&gt;Let me know what you think.&lt;/p&gt;
&lt;p&gt;Best regards&lt;br/&gt;
Wenjamin Rosenfeld&lt;/p&gt;&lt;/div&gt;</summary></entry><entry><title>Output gaussian fit peak position</title><link href="https://sourceforge.net/p/beamprofiler/feature-requests/6/" rel="alternate"/><published>2024-07-11T12:05:23.341000Z</published><updated>2024-07-11T12:05:23.341000Z</updated><author><name>Peter Gribbin</name><uri>https://sourceforge.net/u/pgribbin/</uri></author><id>https://sourceforge.net8bbf6754910b0bb4d8dbb86d8062798faeb36de8</id><summary type="html">&lt;div class="markdown_content"&gt;&lt;p&gt;Thank you for your excellent software. I would like to output the peak position of the fitted gaussian X and Y directions, can you add this feature to the results please?&lt;/p&gt;
&lt;p&gt;My reason for wanting this is that I think the gaussian peak position should be a more noise insensitive metric for laser beam pointing than the COM, COM2 or mid metrics. &lt;/p&gt;
&lt;p&gt;Best regards,&lt;br/&gt;
Peter Gribbin&lt;/p&gt;&lt;/div&gt;</summary></entry></feed>