<?xml version="1.0" encoding="UTF-8"?>
<mantis version="1.2.15" urlbase="https://www.bugs.openpolscope.org/" issuelink="#" notelink="~" format="1">
    <issue>
        <id>87</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1546881165</date_submitted>
        <last_updated>1546881165</last_updated>
        <eta id="10">none</eta>
        <os>Windows</os>
        <platform>Nikon inverted, Ham Flash4</platform>
        <view_state id="10">public</view_state>
        <summary>frame averaging with Flash4 crashes Pol-Acquisition plugin</summary>
        <due_date>1</due_date>
        <description>On Friday, Jan 4, Mai and I used the Nikon inverted stand with the light field camera that now has the new Hamamatsu Flash4 camera with USB connection installed. The Pol-Acquisition plugin in polarized fluorescence mode worked without a hitch, except when we enabled frame averaging. With frame averaging enabled (4 frames), a time series acquisition stalled halfway, and MicroManager needed to be rebooted. Frame averaging seemed to work for some of the acquisitions, but then failed. &#13;
&#13;
Following this experience, we disabled frame averaging (we only recorded sample images, no background was needed), and the rest of the session, taking about 6 hours with many (beautiful) data sets, went flawlessly.</description>
    </issue>
    <issue>
        <id>86</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="60">major</severity>
        <reproducibility id="30">sometimes</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1537907447</date_submitted>
        <last_updated>1537907447</last_updated>
        <eta id="10">none</eta>
        <os>Windows</os>
        <os_build>7</os_build>
        <platform>Nikon inverted station</platform>
        <view_state id="10">public</view_state>
        <summary>switching between birefringence and diattenuation processing</summary>
        <due_date>1</due_date>
        <description>Yesterday, a lab visitor (Inigo Novales) brought a sample (anchovy retina) that required switching between birefringence and diattenuation mode for acquisition and reprocessing (Pol-Analyzer) of such image stacks. During this session, we had to restart the ImageJ-MM program several times, because sometimes, when reprocessing a stack, the result did not appear in the specified stack, but was lost, nobody knows where. Only restart remedied the situation. Also, at least once in diattenuation mode, an incorrect background image was used during processing, even though the correct background was specified in the respective entry.</description>
    </issue>
    <issue>
        <id>85</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1533593090</date_submitted>
        <last_updated>1533593261</last_updated>
        <eta id="10">none</eta>
        <platform>Nikon Ti station</platform>
        <view_state id="10">public</view_state>
        <summary>wavelength change not complete in birefringence mode</summary>
        <due_date>1</due_date>
        <description>After taking retardance images with one wavelength, I changed the wavelength on the scope and entered the new wavelength into the MeadowlarkLC-Controls panel of the Pol-Acquisition window. I then calibrated with the new wavelength, which finished in time, but showed settings for LC-A and LC-B that were quite far off from the usual 0.25 and 0.5. After using the Device Property Browser tool, it calibrated correctly. &#13;
My hunch is that the wavelength is initially not set correctly for the first calibration. Might it first use the default value 546nm?</description>
    </issue>
    <issue>
        <id>84</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1523391626</date_submitted>
        <last_updated>1523391626</last_updated>
        <eta id="10">none</eta>
        <os>All</os>
        <platform>All</platform>
        <view_state id="10">public</view_state>
        <summary>Remove logging of &quot;BG set to...&quot;</summary>
        <due_date>1</due_date>
        <description>&quot;BG set to...&quot; unnecessarily often in the Log and can be dropped altogether. &#13;
It is sufficient that the BG is recorded in the metadata to each image.</description>
    </issue>
    <issue>
        <id>83</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1522507746</date_submitted>
        <last_updated>1522507746</last_updated>
        <eta id="10">none</eta>
        <os>OSX</os>
        <platform>Macintosh</platform>
        <view_state id="10">public</view_state>
        <summary>Pol-Analyzer Data Session pull down list seems randomly ordered in session names</summary>
        <due_date>1</due_date>
        <description>Pol-Analyzer Data Session pull down list seems randomly ordered in session names</description>
    </issue>
    <issue>
        <id>82</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1522443299</date_submitted>
        <last_updated>1522443299</last_updated>
        <eta id="10">none</eta>
        <os>Windows</os>
        <platform>Ti-E workstation</platform>
        <view_state id="10">public</view_state>
        <summary>swing value logged for diattenuation setting</summary>
        <due_date>1</due_date>
        <description>A swing value is logged when diattenuation setting is enabled.&#13;
There is no swing value for diattenuation</description>
    </issue>
    <issue>
        <id>81</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <priority id="30">normal</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1522094937</date_submitted>
        <last_updated>1522094937</last_updated>
        <eta id="10">none</eta>
        <os>Windows</os>
        <os_build>10</os_build>
        <platform>Workstation at Nikon Ti-E Inv.</platform>
        <view_state id="10">public</view_state>
        <summary>Pol-Analysis,&quot;Use ROI from Sample Metadata from Background&quot; toggles on/off indefinitely</summary>
        <due_date>1</due_date>
        <description>In Pol-Analysis, after opening BG stack, &quot;Use ROI from Sample Metadata from Background&quot; toggles on/off indefinitely</description>
    </issue>
    <issue>
        <id>80</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1522091844</date_submitted>
        <last_updated>1522091844</last_updated>
        <eta id="10">none</eta>
        <os>Windows</os>
        <os_build>10</os_build>
        <platform>Workstation at Nikon Ti-E Inv.</platform>
        <view_state id="10">public</view_state>
        <summary>Acquired Diatt. Stack shows only 6 out of 7 slices</summary>
        <due_date>1</due_date>
        <description>The data set is saved correctly, but incompletely displayed after acquisition.&#13;
Loading the data set with Pol-Analyzer displays all slices</description>
    </issue>
    <issue>
        <id>79</id>
        <project id="17">Birefringence</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1489354218</date_submitted>
        <last_updated>1489354218</last_updated>
        <eta id="10">none</eta>
        <os>MacOS </os>
        <os_build>10.12.3</os_build>
        <version>2.2</version>
        <view_state id="10">public</view_state>
        <summary>Pol-Analyzer, new Logger text not loaded, etc.</summary>
        <due_date>1</due_date>
        <description>1. New Logger text not loaded (visible) after switching to new session.&#13;
&#13;
This seems to happen only after at least one polstack was opened. &#13;
&#13;
When testing it without opening a polstack after restart, the Logger text will show fine.&#13;
&#13;
Once the Logger text doesn't show, only quitting MM and restarting it will make the Logger text reappear.&#13;
&#13;
2. When starting MM and then Pol-Analyzer plugin, the default session is not the session that was active before last quit, unless the Pol-Analyzer plugin was closed and reopened during the last session.&#13;
&#13;
3. Sometimes the &quot;Editable Info&quot; in session.polSession is inappropriately overwritten. Also, it seems that this info in the Mac version of Pol-Analyzer plugin is added to the end of the session.polSession file, while the Windows version puts it at the beginning of the file.</description>
    </issue>
    <issue>
        <id>78</id>
        <project id="18">Diattenuation</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1460215002</date_submitted>
        <last_updated>1460215002</last_updated>
        <eta id="10">none</eta>
        <platform>All</platform>
        <view_state id="10">public</view_state>
        <summary>ratio value decimal readout</summary>
        <due_date>1</due_date>
        <description>Increase decimals in displayed/printed ratio values from 1 to 3.&#13;
&#13;
For example, display ratio value 1.123 instead of 1.1 </description>
    </issue>
    <issue>
        <id>77</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <priority id="30">normal</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1444677394</date_submitted>
        <last_updated>1444677394</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>orientation cursor for z-stack</summary>
        <due_date>1</due_date>
        <description>orientation cursor for z-stack not reading correct azimuth values&#13;
possibly only for first z-slice correct</description>
    </issue>
    <issue>
        <id>76</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1443473405</date_submitted>
        <last_updated>1443473405</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>In diattenuation mode image path mirror setting inactive</summary>
        <due_date>1</due_date>
        <description>Make image path mirror setting active</description>
    </issue>
    <issue>
        <id>75</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1443048880</date_submitted>
        <last_updated>1443048880</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>MO device delay inactive by default</summary>
        <due_date>1</due_date>
        <description>MO device delay inactive by default, becomes active after entering delay in Property Browser, observed in Diattenuation mode.</description>
    </issue>
    <issue>
        <id>74</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="60">major</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1443039881</date_submitted>
        <last_updated>1443040313</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>Keep shutter open during pol acquisition sequence</summary>
        <due_date>1</due_date>
        <description>Keep shutter open during pol acquisition sequence and calibration&#13;
</description>
    </issue>
    <issue>
        <id>73</id>
        <project id="5">Pol-Analyzer</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1441398728</date_submitted>
        <last_updated>1441398728</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>remove aBg and bBg from Polarized Fluorescence tab</summary>
        <due_date>1</due_date>
        <description>remove aBg and bBg from bottom of Polarized Fluorescence tab</description>
    </issue>
    <issue>
        <id>72</id>
        <project id="5">Pol-Analyzer</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1441395557</date_submitted>
        <last_updated>1441395557</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>Dialog for opening MMPolStack always starts inside first SM... folder</summary>
        <due_date>1</due_date>
        <description>Dialog should start with session folder.</description>
    </issue>
    <issue>
        <id>71</id>
        <project id="23">MeadowlarkLC</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="60">major</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1440440343</date_submitted>
        <last_updated>1440440343</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>Birefringence acquisition: LC settings not recorded in metadata of raw images</summary>
        <due_date>1</due_date>
        <description>In the metadata of the raw images, the palette elements are empty and the Retardance LC-A and LC-B show what I think are the values for the extinction setting for all elliptical settings as well. </description>
    </issue>
    <issue>
        <id>70</id>
        <project id="19">Fluorescence Polarization</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1440366859</date_submitted>
        <last_updated>1440381360</last_updated>
        <eta id="10">none</eta>
        <platform>Pol-Analyzer</platform>
        <view_state id="10">public</view_state>
        <summary>Error on first reprocess of Pol-fluorescence images</summary>
        <due_date>1</due_date>
        <description>After clicking Process, error message &quot;Images with more than 7 channels cannot be displayed in Composite mode&quot;.&#13;
&#13;
After clicking OK on this error message, reprocessing the same image completes correctly, without error message.&#13;
&#13;
Opening a new polstack and processing it will again trigger the error message, while the second processing will again complete correctly.</description>
    </issue>
    <issue>
        <id>69</id>
        <project id="19">Fluorescence Polarization</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="40">high</priority>
        <severity id="70">crash</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="4">micro-manager bug</category>
        <date_submitted>1440357170</date_submitted>
        <last_updated>1440357170</last_updated>
        <eta id="10">none</eta>
        <platform>Nikon inverted/Flash4/MLO-LCs</platform>
        <view_state id="10">public</view_state>
        <summary>First acquisition stalls</summary>
        <due_date>1</due_date>
        <description>After starting ImageJ/MM/Pol-Acquisition the first time, the first pol-acquisition using either BG or SM stalls, never completes and prevents closing of ImageJ/MM. However, the Pol-Acquistion window can be closed. &#13;
&#13;
After ending javaw.exe process and restarting ImageJ/MM/Pol-Acquisition, all further acquisition requests execute correctly.</description>
    </issue>
    <issue>
        <id>68</id>
        <project id="19">Fluorescence Polarization</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="1">General</category>
        <date_submitted>1440355554</date_submitted>
        <last_updated>1440355554</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>Change Fluorescence Polarization to Polarized Fluorescence</summary>
        <due_date>1</due_date>
        <description>In OPS environment, change all occurrences of Fluorescence Polarization to Polarized Fluorescence</description>
    </issue>
    <issue>
        <id>65</id>
        <project id="23">MeadowlarkLC</project>
        <reporter id="10">Mai Tran</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="30">sometimes</reproducibility>
        <status id="80">resolved</status>
        <resolution id="70">no change required</resolution>
        <projection id="10">none</projection>
        <category id="4">micro-manager bug</category>
        <date_submitted>1387904413</date_submitted>
        <last_updated>1387935588</last_updated>
        <eta id="10">none</eta>
        <view_state id="10">public</view_state>
        <summary>Micro-Manager errors</summary>
        <due_date>1</due_date>
        <description>When I opened Micro-Manager I saw this massage below:&#13;
&#13;
&quot;Line 16: Property,MeadowlarkLC,Number of Active LCs,2&#13;
Error in device MeadowlarkLC: Invalid property name encountered: Number of Active LCs. (Error code: 2)&#13;
&#13;
&#13;
Line 17: Property,MeadowlarkLC,Select Device #,1&#13;
Error in device MeadowlarkLC: Invalid property value: Select Device #. (Error code: 3)&#13;
&#13;
&#13;
Line 18: Property,MeadowlarkLC,Select Device Type,20V (D3060HV) Controller&#13;
Error in device MeadowlarkLC: Invalid property name encountered: Select Device Type. (Error code: 2)&#13;
&#13;
&#13;
Line 19: Property,MeadowlarkLC,Serial/Version No.,123&#13;
Error in device MeadowlarkLC: Invalid property name encountered: Serial/Version No.. (Error code: 2)&#13;
&#13;
&#13;
Line 20: Property,MeadowlarkLC,Total Number of LCs,4&#13;
Error in device MeadowlarkLC: Invalid property name encountered: Total Number of LCs. (Error code: 2)&#13;
&#13;
&#13;
Line 21: Property,MeadowlarkLC,Total Number of Palette Elements,5&#13;
Error in device MeadowlarkLC: Invalid property name encountered: Total Number of Palette Elements. (Error code: 2)&#13;
&#13;
&#13;
Line 30: Property,Core,Initialize,1&#13;
Error in device MeadowlarkLC: Unable to communicate with the device.. &#13;
&#13;
&#13;
Line 37: Property,Core,Camera,Hamamatsu_DCAM&#13;
Attempted to set &quot;Core-Camera&quot; to &quot;Hamamatsu_DCAM&quot;.&#13;
Core property is read-only or the requested value is not allowed.&#13;
&#13;
Line 38: Property,Core,Focus,TIZDrive&#13;
Attempted to set &quot;Core-Focus&quot; to &quot;TIZDrive&quot;.&#13;
Core property is read-only or the requested value is not allowed.&quot;&#13;
&#13;
However it seems there are some problems with my computer as well. It doesn't see the usb so it might not see the LCs. Otherwise I don't know.</description>
    </issue>
    <issue>
        <id>34</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="2">amit</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1372835118</date_submitted>
        <last_updated>1379619180</last_updated>
        <eta id="10">none</eta>
        <version>2.1</version>
        <target_version>2.2</target_version>
        <view_state id="10">public</view_state>
        <summary>List of actions that report to Logger panel</summary>
        <due_date>1</due_date>
        <description>List of actions that report to Logger panel:&#13;
&#13;
Currently implemented.&#13;
1. Acquiring SM, BG, Series with comment&#13;
2. Creating new user, session&#13;
3. Changing Mode Plugin&#13;
4. Acquiring non Pol image via Album button&#13;
5. Calibrating Diattenuation, FluorPol (Anisotropy, Orientation)&#13;
&#13;
To implement.&#13;
&#13;
&#13;
Recently Implemented.&#13;
1. Implement in Pol-Analyzer&#13;
2. Birefringence calibration</description>
    </issue>
    <issue>
        <id>58</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="20">feedback</status>
        <resolution id="30">reopened</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1379271547</date_submitted>
        <last_updated>1379530807</last_updated>
        <eta id="10">none</eta>
        <os>Windows 7</os>
        <version>2.17</version>
        <fixed_in_version>2.17</fixed_in_version>
        <view_state id="10">public</view_state>
        <summary>Enable interupt when drawing orientation lines</summary>
        <due_date>1</due_date>
        <description>When drawing orientation lines is set to every pixel (interval=1), it can take a long time (~30 sec)for the lines to show when image is large (2,000x2,000.&#13;
&#13;
Enable to cancel the lines by removing (unclicking) the checkmark</description>
    </issue>
    <issue>
        <id>63</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="100">N/A</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="9">feature-request</category>
        <date_submitted>1379368697</date_submitted>
        <last_updated>1379368697</last_updated>
        <eta id="10">none</eta>
        <os>Windows 7</os>
        <version>2.17</version>
        <view_state id="10">public</view_state>
        <summary>Create default settings using current swing setting</summary>
        <due_date>1</due_date>
        <description>I suggest to create the default settings using the current swing value</description>
    </issue>
    <issue>
        <id>62</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1379272401</date_submitted>
        <last_updated>1379336120</last_updated>
        <eta id="10">none</eta>
        <os>Windows 7</os>
        <version>2.17</version>
        <view_state id="10">public</view_state>
        <summary>Pol-Analyzer, draws orientation lines even if not selected</summary>
        <due_date>1</due_date>
        <description>When reprocessing a sample image, orientation lines were drawn, even if not selected.</description>
    </issue>
    <issue>
        <id>60</id>
        <project id="4">Pol-Acquisition</project>
        <reporter id="3">rudolfo</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="10">always</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="2">bug</category>
        <date_submitted>1379272191</date_submitted>
        <last_updated>1379272191</last_updated>
        <eta id="10">none</eta>
        <os>Windows 7</os>
        <version>2.17</version>
        <view_state id="10">public</view_state>
        <summary>List of window titles in ImageJ&gt;Windows is mixed up</summary>
        <due_date>1</due_date>
        <description>MM stacks in ImageJ&gt;Windows menu are incorrectly named.</description>
    </issue>
    <issue>
        <id>25</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="1">admin</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1372555745</date_submitted>
        <last_updated>1376172143</last_updated>
        <eta id="10">none</eta>
        <version>2.15</version>
        <target_version>2.18</target_version>
        <view_state id="10">public</view_state>
        <summary>Show Invalid Pixels</summary>
        <due_date>1</due_date>
        <description>Use an overlay to color (say red) any pixels in a computed image where the the value of this pixel in any of the sample images is saturated.</description>
    </issue>
    <issue>
        <id>55</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="2">amit</reporter>
        <handler id="2">amit</handler>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1376169919</date_submitted>
        <last_updated>1376172078</last_updated>
        <eta id="10">none</eta>
        <version>2.16</version>
        <target_version>2.17</target_version>
        <view_state id="10">public</view_state>
        <summary>sub-plugins should work with stack option disabled in Pol-Analyzer Options</summary>
        <due_date>1</due_date>
        <description>Sub-plugins (eg. ColorMap) should work with stack option disabled in Pol-Analyzer Options. This is useful to export a selected timepoint/z-plane without reprocessing the complete stack and then exporting the required image.</description>
    </issue>
    <issue>
        <id>32</id>
        <project id="1">OpenPolScope-API</project>
        <reporter id="4">shalin</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="9">feature-request</category>
        <date_submitted>1372812012</date_submitted>
        <last_updated>1376171855</last_updated>
        <eta id="10">none</eta>
        <version>2.15</version>
        <target_version>2.2</target_version>
        <view_state id="10">public</view_state>
        <summary>Enable calling Pol-Analyzer's data-conversion functions from MATLAB</summary>
        <due_date>1</due_date>
        <description>It will be efficient if users can transparently get data computed by MATLAB converted into format compatible with Pol-analyzer. My prefeered workflow would be like this (using Fiji):&#13;
&gt;Miji(false);&#13;
&gt;MIJ.Run('Pol-AnalyzerDataConverter','PathtoTifffile.tif');&#13;
&#13;
It is OK to overwrite the tif file Pol-Analyzer format data.</description>
    </issue>
    <issue>
        <id>52</id>
        <project id="27">Orientation Lines V4</project>
        <reporter id="1">admin</reporter>
        <handler id="5">grant</handler>
        <priority id="50">urgent</priority>
        <severity id="10">feature</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="50">assigned</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1375483386</date_submitted>
        <last_updated>1375483449</last_updated>
        <eta id="10">none</eta>
        <version>2.15</version>
        <target_version>2.16</target_version>
        <view_state id="10">public</view_state>
        <summary>glyphs / circular statistics for Orientation lines</summary>
        <due_date>1</due_date>
        <description>add glyphs / circular statistics / additions from Grant/Rudolf/Hannah's code&#13;
&#13;
Added by Shalin:&#13;
&#13;
We have been using Pol-Analyzer for exploring data taken in&#13;
collaboration with Clare Waterman's group (mostly real-time PolScope&#13;
data converted to MM format) and with Daniel Gerlich (Nikon PolScope).&#13;
&#13;
In both cases, we need to compare average anisotropy/orientation in&#13;
following ways:&#13;
a) When the lines are plotted every Nth pixel, it is expected that&#13;
intensity is averaged over NXN pixels before the&#13;
anisotropy/orientation are calculated and plotted. We can plot the&#13;
orientation line at the center of NXN pixels.&#13;
b) Often times the biologically interesting measurement is to compare&#13;
net anisotropy over manually selected regions. We would like to draw a&#13;
ROI manually and obtain anisotropy/orientation using intensities&#13;
averaged over that ROI.&#13;
c) An extension of b) for rectangular ROI is that the ROI can be&#13;
partitioned into rows and columns with anisotropy/orientation obtained&#13;
over each sub-ROI (the mode that Rudolf implemented with ROI averages&#13;
with Lines V1).&#13;
&#13;
For b) and c) an option to plot orientation fan (displaying average&#13;
orientation and its variance as Grant has implemented) will be quite&#13;
informative.&#13;
&#13;
It seems that a) is properly implemented within current Azim Lines&#13;
plugin as an option.&#13;
&#13;
It seems that b) and c) can be made by combining Rudolf's plugin and&#13;
Grant's orientation fan. If we can bump these feature requests higher&#13;
in priority, they can receive good use and testing over next few&#13;
weeks.&#13;
&#13;
Also, it is important to be able to export the values, for example by&#13;
pushing them to the measurement window of ImageJ.&#13;
</description>
        <additional_information>moved from Orientation Lines V3 project (Issue #24)</additional_information>
    </issue>
    <issue>
        <id>26</id>
        <project id="18">Diattenuation</project>
        <reporter id="1">admin</reporter>
        <priority id="30">normal</priority>
        <severity id="50">minor</severity>
        <reproducibility id="70">have not tried</reproducibility>
        <status id="10">new</status>
        <resolution id="10">open</resolution>
        <projection id="10">none</projection>
        <category id="3">enhancement</category>
        <date_submitted>1372555836</date_submitted>
        <last_updated>1375482613</last_updated>
        <eta id="10">none</eta>
        <version>2.1</version>
        <target_version>2.2</target_version>
        <view_state id="10">public</view_state>
        <summary>UI for Calibration Process</summary>
        <due_date>1</due_date>
        <description>Not evident that one can EITHER use 'Single ROI Calibration' or 'Four ROI calibration' method. Perhaps have a radio button to choose one or the other, and enable the panel for the chosen method.</description>
    </issue>
</mantis>
