Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
General / Re: Color cast with PhotometricColorCalibration
« Last post by Alejandro Tombolini on 2019 May 19 19:43:41 »
Hi Scott, I did color calibration in your image using PCC. You can follow the steps here. Hope this helps.

Saludos, Alejandro.
22
Bug Reports / Re: a little help please with repository Error 400
« Last post by Herbert_W on 2019 May 19 17:28:43 »
Hi Andy!

Leave out the s in https - with some Windows operating systems (especially win7) it only works with http://www.skypixels.at/HVB_Repository/

Best regards!
Herbert, Austria
23
Bug Reports / a little help please with repository Error 400
« Last post by Andyc421 on 2019 May 19 16:28:29 »

Hi folks
any advice on how to fix the following error code

https://www.skypixels.at/HVB_Repository/to RESOURCES / Updates / Manage Repositories./: Network error: Response code = 400

thank you in advance for your help
Andy
24
Announcements / Re: PixInsight 1.8.6.1473 Released
« Last post by Juan Conejero on 2019 May 19 14:08:08 »
Hi Conor,

I'm very keen to get back to processing with PI as my main workhorse, so if I can offer any help, let me know!

I have very good news. I have now a working virtual machine with FreeBSD 12.0 and the latest version of KDE Plasma installed and running nicely. It includes Qt 5.12.1, so... :)
25
Announcements / Re: PixInsight 1.8.6.1473 Released
« Last post by Juan Conejero on 2019 May 19 14:05:32 »
Gordon,

This bug is now fixed with a set of updates I have just released, including a new build 1475 of the PixInsight core application and several processes. Sorry for the trouble, and thank you for your patience.
26
This bug is now fixed with the release of several updates, including a new build 1475 of the PixInsight core application. Thank you for your patience.
27
Bug Reports / Re: Image Solver problems
« Last post by Juan Conejero on 2019 May 19 14:01:41 »
Yes, this is by design. A warning message is now shown when trying to solve an image without knowing an actual acquisition date, either automatically gathered from existing metadata, or entered manually. With the increased accuracy of the new distortion modeling algorithm that we have implemented in the ImageSolver script, computing accurate star proper motions is critical.
28
Bug Reports / Re: Image Solver problems
« Last post by SteveTeel on 2019 May 19 12:38:49 »
I notice that in the 1474 release the Epoch parameter is missing from the Image Solver script. If the image comes from a data source that does not record the DATE-OBS keyword, one must be sure to enter it using the FITS Header process.
29
General / Re: Warning While Doing ImageIntegration?
« Last post by Don on 2019 May 19 11:04:10 »
Hi Juan,

The data files were acquired with Sequence Generator Pro (SGP), and that is where the FITS keywords were generated and added to the files.  The format of the SITELAT and SITELONG keywords generated by SGP has not changed recently.  These errors did not occur until the recent update to PixInsight version 1.08.06.1473, and today's update to 1.08.06.1474 still produces the error.  Data files that processed without error in previous versions of PixInsight now produce these errors.  So obviously something changed in PI 1.08.06.1473.  Apparently you were not trying to parse these keyword values as numbers in ImageIntegration previously - in data files calibrated last month with the previous PI version, the SITELAT and SITELONG keywords were passed into the calibrated files as strings, in the same format that they are in now, but are not present in the integrated files.  In 1.08.06.1473, SITELAT and SITELONG are still passed to the calibrated files as strings, and subsequent processing maintains them as strings until ImageIntegration fails while trying to parse them as numbers.

I'm easy - I don't need the SITELAT and SITELONG data, so to me the error is inconsequential, since ImageIntegration continues and produces the desired output file.  The user provides the latitude and longitude for each site in SGP, but cannot control the format of the FITS keywords.  If you are planning to use these values in future PI versions, some kind of resolution will need to occur.  If not, it is probably better to stop trying to parse them in ImageIntegration, but just pass them as strings if at all.

I will submit a defect report to SGP, citing the document you reference here. 

Don
30
General / Re: Warning While Doing ImageIntegration?
« Last post by Juan Conejero on 2019 May 19 08:47:48 »
This is a completely different problem:

34d4m30.000s N
84d34m40.000s W

These are invalid values for the SITELAT and SITELONG keywords. See the SBIG proposal for FITS keyword extensions document. The expected format for these nonstandard keywords is the same as OBJCTDEC, that is, 'DDD MM SS.sss'. Another example of the endless universe of FITS interoperability problems.
Pages: 1 2 [3] 4 5 ... 10