April 10, 2007, at 10:24 AM
by mkeith -
Changed line 38 from:
Candidate lists writen back to wrong location
to:
Candidate lists writen back to wrong location
April 10, 2007, at 10:24 AM
by mkeith -
Changed lines 38-39 from:
to:
Candidate lists writen back to wrong location
Data written to results root rather than the correct subdirectory
April 10, 2007, at 10:22 AM
by mkeith -
Changed lines 10-12 from:
- No close button on PHCF plots in JReaper or ph-view-phcf - Fixed as of 1.2.5
- Some data is lost off the bottom due to badly specified plot sizes
- Acceleration curve etc should ignore 0 value points (due to not all dms having all points) - Fixed as of 1.2.5
to:
- No close button on PHCF plots in ph-view-phcf
Changed lines 33-39 from:
to:
PHCF plots in JReaper and ph-view-phcf
- No close button on PHCF plots in JReaper
- Some data is lost off the bottom due to badly specified plot sizes
- Acceleration curve etc should ignore 0 value points (due to not all dms having all points)
April 10, 2007, at 10:21 AM
by mkeith - Moved some bugs to fixed as of 1.2.5
Changed lines 7-8 from:
Current as of 1.2.4
to:
Current as of 1.2.5
Added lines 27-30:
April 10, 2007, at 06:13 AM
by mkeith -
Changed lines 1-2 from:
PulsarHunter Known Issues
to:
April 10, 2007, at 06:13 AM
by mkeith -
Changed lines 3-6 from:
to:
Please use the Bug Tracker for new bugs!
April 10, 2007, at 05:58 AM
by mkeith -
Changed line 7 from:
- No close button on PHCF plots in JReaper or ph-view-phcf
to:
- No close button on PHCF plots in JReaper or ph-view-phcf - Fixed as of 1.2.5
Changed line 9 from:
- Acceleration curve etc should ignore 0 value points (due to not all dms having all points)
to:
- Acceleration curve etc should ignore 0 value points (due to not all dms having all points) - Fixed as of 1.2.5
April 09, 2007, at 06:57 AM
by mkeith -
Changed lines 27-28 from:
ph-view-phcf candidate plot needs to be larger since the pre and post optimised parameters are not instantly visible
to:
April 04, 2007, at 04:36 AM
by mkeith -
Changed lines 27-28 from:
to:
ph-view-phcf candidate plot needs to be larger since the pre and post optimised parameters are not instantly visible
Deleted line 34:
ph-view-phcf candidate plot needs to be larger since the pre and post optimised parameters are not instantly visible
April 04, 2007, at 02:37 AM
by Ralph Eatough - ph-view-phcf candidate plot dimensions
Added lines 33-35:
ph-view-phcf candidate plot needs to be larger since the pre and post optimised parameters are not instantly visible
March 23, 2007, at 08:03 AM
by mkeith -
Added lines 13-16:
Files are saved even if they are unmodified
Causes errors when no write permissions, and does unnecessary disk writes.
March 23, 2007, at 08:02 AM
by mkeith -
Changed lines 5-6 from:
No close button on PHCF plots in JReaper or ph-view-phcf
to:
PHCF plots in JReaper and ph-view-phcf
- No close button on PHCF plots in JReaper or ph-view-phcf
- Some data is lost off the bottom due to badly specified plot sizes
- Acceleration curve etc should ignore 0 value points (due to not all dms having all points)
- Score breakdown should be visible somewhere
March 23, 2007, at 05:22 AM
by mkeith -
Added lines 5-9:
No close button on PHCF plots in JReaper or ph-view-phcf
Errors generated when loading data library, even if data library loaded ok
Probably caused by trying to switch windows before the whole DL is loaded.
March 22, 2007, at 08:08 AM
by mkeith -
Changed lines 3-5 from:
Affecting current version
These issues are still present as of v1.2.0
to:
Current as of 1.2.4
Changed lines 9-15 from:
Folding error misplaces one bin (Fixed in next release)
to:
Exits ungracefully when trying to auto detect the type of an unknown file.
Returns things line null pointer exception, instead of testing that the file exits.
Fixed as of 1.2.4
Folding error misplaces one bin (Fixed in 1.2.4)
February 20, 2007, at 07:06 AM
by mkeith -
Added lines 9-12:
Folding error misplaces one bin (Fixed in next release)
For the first half of the timeseries, what should be the last output bin is placed in the second last.
This effectively breaks folding for un-baselined data.
February 15, 2007, at 04:43 PM
by mkeith -
Added lines 1-8:
PulsarHunter Known Issues
Affecting current version
These issues are still present as of v1.2.0
Sigproc data reading limitations
Currently pulsarhunter will only read 32bit floating point timeseries.
If a timeseries with a different number of bits is read, PulsarHunter will not detect the file as a known file type.