https://bugs.kde.org/show_bug.cgi?id=479457
Wolfgang Reissenberger changed:
What|Removed |Added
CC||wreis...@gmx.de
Status
https://bugs.kde.org/show_bug.cgi?id=471373
Wolfgang Reissenberger changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--- Comment #4 from Wolfgang
https://bugs.kde.org/show_bug.cgi?id=471373
Wolfgang Reissenberger changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=465324
--- Comment #6 from Wolfgang Reissenberger ---
closed
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465324
Wolfgang Reissenberger changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=464775
--- Comment #1 from Wolfgang Reissenberger ---
There is no stable way to reproduce this issue. I can confirm, I could observe
it and that there were situations when the target was not set. But after
recompiling everything it *seems* to work - no matter
https://bugs.kde.org/show_bug.cgi?id=451687
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=452794
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Assignee|mutla
https://bugs.kde.org/show_bug.cgi?id=436036
Wolfgang Reissenberger changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |wreis...@gmx.de
Status
https://bugs.kde.org/show_bug.cgi?id=451687
Wolfgang Reissenberger changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |wreis...@gmx.de
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=451532
Wolfgang Reissenberger changed:
What|Removed |Added
CC||wreis...@gmx.de
Assignee
https://bugs.kde.org/show_bug.cgi?id=451687
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC
https://bugs.kde.org/show_bug.cgi?id=441164
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
--- Comment #3 from Wolfgang
https://bugs.kde.org/show_bug.cgi?id=441164
Wolfgang Reissenberger changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=441164
Wolfgang Reissenberger changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=416173
Bug ID: 416173
Summary: EKOS hangs when an INDI driver crashes
Product: kstars
Version: 3.3.9
Platform: Debian stable
OS: Linux
Status: REPORTED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=409125
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=409125
--- Comment #8 from Wolfgang Reissenberger ---
Ah, I found the problem. In my simulator setup, I had dome radius etc. all set
to 0. When I set the dome radius to 5m, it's working fine.
OK, should be ready for testing. I posted a new diff:
https://bugs.kde.org/show_bug.cgi?id=409125
--- Comment #4 from Wolfgang Reissenberger ---
Jean-Claude,
I need you help for testing, since I am not sure whether slaving is working
appropriately. Could you please check out the branch observatory_work_motion
from my kstars clone:
https
https://bugs.kde.org/show_bug.cgi?id=409125
--- Comment #2 from Wolfgang Reissenberger ---
The buttons for moving the dome and one for abort is more or less straight
forward. But what functionality do you expect from the slaving button?
For me it looks like it is OK when slaving is set up in
https://bugs.kde.org/show_bug.cgi?id=409125
--- Comment #1 from Wolfgang Reissenberger ---
OK, I'll do my best.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405325
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=405325
--- Comment #16 from Wolfgang Reissenberger ---
Bug fix posted here: https://phabricator.kde.org/D19794
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=405325
--- Comment #14 from Wolfgang Reissenberger ---
While testing the fix to the status message, I found a more severe one:
- set "Meridian Flip..." in the mount module NOT ticked
- start a capturing session close to the meridian with &quo
https://bugs.kde.org/show_bug.cgi?id=405325
Wolfgang Reissenberger changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=405325
--- Comment #9 from Wolfgang Reissenberger ---
A possible explanation is that the time of your mount and that of the device
running Ekos are not in sync. The meridian flip relies on the ability of the
mount slewing to a point that is meanwhile beyond
https://bugs.kde.org/show_bug.cgi?id=405325
--- Comment #7 from Wolfgang Reissenberger ---
Oha, OK, never heard that observatories execute a meridian flip :)
I will give it a try with a simulator setup, since I do not have an observatory
at hand to test it in real life.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=405325
--- Comment #3 from Wolfgang Reissenberger ---
Jean-Claude, could you please be a little more specific, what the problem is?
Here some background how it is built: the meridian flip is controlled by the
Mount module. At the same time, in a capture
https://bugs.kde.org/show_bug.cgi?id=402709
--- Comment #2 from Wolfgang Reissenberger ---
The latest commit on the master branch is
2bd1ad0433ce9a0cabce2b693ebc4bc50be6e703
It seems like lightFramesRequired is not used properly, since it does not take
into account, whether the image sequence
https://bugs.kde.org/show_bug.cgi?id=402709
Wolfgang Reissenberger changed:
What|Removed |Added
Assignee|mutla...@ikarustech.com |eric.dejouha...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=402709
Bug ID: 402709
Summary: scheduler does not start a sequence when frames exist
although repeat until terminated is selected
Product: kstars
Version: 3.0.1
Platform: Compiled Source
https://bugs.kde.org/show_bug.cgi?id=400265
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=400265
--- Comment #7 from Wolfgang Reissenberger ---
Bug fix diff submitted: https://phabricator.kde.org/D17159
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400265
--- Comment #6 from Wolfgang Reissenberger ---
It looks like the Capture module cannot detect the necessity of a meridian flip
upfront.
The Capture module records the initial hour angle. If the initial hour angle is
already west of the meridian, the
https://bugs.kde.org/show_bug.cgi?id=400265
--- Comment #4 from Wolfgang Reissenberger ---
Well, promising that it does not cause any regressions is challenging for the
Capture module :-/
But sure, yes, I will give it a try.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=400265
--- Comment #2 from Wolfgang Reissenberger ---
What about shifting (or adding) this check to preparePreCaptureActions()?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=400265
Bug ID: 400265
Summary: Schedule with single frame capture does not initiate
meridian flip
Product: kstars
Version: 3.0.1
Platform: Other
OS: Linux
Sta
https://bugs.kde.org/show_bug.cgi?id=398466
Bug ID: 398466
Summary: No delay before first image possible
Product: kstars
Version: 2.9.8
Platform: unspecified
OS: All
Status: UNCONFIRMED
Severity: wishlist
https://bugs.kde.org/show_bug.cgi?id=398165
--- Comment #2 from Wolfgang Reissenberger ---
Oh, sorry, from the logs it seemed to be ready.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=398165
Bug ID: 398165
Summary: [dbus_work] core dump when starting scheduler
Product: kstars
Version: unspecified
Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #14 from Wolfgang Reissenberger ---
I am still searching for the best way to restructure it. Maybe a very helpful
first step is simply changing the method names to be more meaningful:
processPreCaptureCalibrationStage
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #13 from Wolfgang Reissenberger ---
Yepp, parking mount and dome can be controlled through the calibration dialog.
Flat field calibration can be fixed with D14977. The only problem is that my
posted diff contains more than my correction of
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #11 from Wolfgang Reissenberger ---
The entire control flow of Capture is very tricky. Here some examples:
- Preparing CCD temperature, filter, rotator, gain, ... is controlled by
SequenceJob.
- Setting up the equipment - dust cap, flat
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #10 from Wolfgang Reissenberger ---
The hotfix based on getCount() solved the problem, but now the preview mode is
cycling infinitely. We need a different approach to separate a preview
initiated by pressing the "Preview" b
https://bugs.kde.org/show_bug.cgi?id=397776
Wolfgang Reissenberger changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status
https://bugs.kde.org/show_bug.cgi?id=397776
Bug ID: 397776
Summary: Aborted job with given startup time not restarted
Product: kstars
Version: 2.9.8
Platform: unspecified
OS: unspecified
Status: UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #8 from Wolfgang Reissenberger ---
The hot fix is submitted as #D14977.
Further refactoring is not so easy :(
There are in essence one where flats handling is extensively intertwined:
processPreCaptureCalibrationStage()
But I do not
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #7 from Wolfgang Reissenberger ---
OK, I'll take over.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #5 from Wolfgang Reissenberger ---
I could take over this point, sure. Just give me a hint whether you started
already. It does not get better when it is done twice :-)
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=397650
--- Comment #2 from Wolfgang Reissenberger ---
I would also prefer replacing seqTotalCount by activeJob->getCount(), since
caching the value always bears the risk that the value is not up to date. By
the way, seqTotalCount is no longer used, o
https://bugs.kde.org/show_bug.cgi?id=397650
Bug ID: 397650
Summary: Flats creation fails
Product: kstars
Version: 2.9.8
Platform: unspecified
OS: Linux
Status: UNCONFIRMED
Severity: major
Priorit
https://bugs.kde.org/show_bug.cgi?id=397227
--- Comment #2 from Wolfgang Reissenberger ---
Tested it on commit 9c7bebf8421ce49194ebed7ecdaa426ac143032d. Looks good!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=397227
Bug ID: 397227
Summary: PHD2 stopped guiding not recognized
Product: kstars
Version: 2.9.7
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Severity: major
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #12 from Wolfgang Reissenberger ---
Yes, Eric made several very good comments. I made all changes he suggested and
submitted a new version: https://phabricator.kde.org/D14309
For rebasing: please advise, I do not exactly know what to do
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #10 from Wolfgang Reissenberger ---
Bug fix submitted as https://phabricator.kde.org/D14280
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #9 from Wolfgang Reissenberger ---
OK, thanks for the hint. I've installed arc and will try to use it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #7 from Wolfgang Reissenberger ---
OK, I'll take over. I should place the patch through Phabricator, right?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #5 from Wolfgang Reissenberger ---
Great! If you need bandwidth, I could take over the fix as well.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=396742
--- Comment #3 from Wolfgang Reissenberger ---
I took a closer look into the Capture class. There is an approach counting
existing images across all sequences. But there is no counterpart determining
the target counts of images spanning the contained
https://bugs.kde.org/show_bug.cgi?id=396742
Bug ID: 396742
Summary: EKOS | Capture | multiple occurrence of the same
sequence job ignored
Product: kstars
Version: 2.9.5
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=394725
--- Comment #2 from Wolfgang Reissenberger ---
I have resolved it meanwhile. Please see my patch here:
https://phabricator.kde.org/D14149
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=394725
Bug ID: 394725
Summary: crash while shooting flats
Product: kstars
Version: 2.9.5
Platform: Debian stable
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
62 matches
Mail list logo
