Star Tracer optimalization problem["Double" type c

Discussion forum for Tawbaware's Star Tracer and Image Stacker software
Post Reply
mikepapa
Posts: 1
Joined: Sun Oct 03, 2010 8:06 pm

Star Tracer optimalization problem["Double" type c

Post by mikepapa » Sun Oct 03, 2010 8:16 pm

I just downloaded Star Tracer, and when I try to use optimalization, I get following results:

02:11:54 Starting process
02:11:54 Process returned: 0
02:11:55 Parsing script
02:11:55 Error 13:Konwersja z ciągu "0.000000" na typ 'Double' nie jest prawidłowa. parsing line: o f0 y0.000000 p7.692514 r43.465762 A0.00000000 B0.00000000 C0.00000000 D0.00000000 E0.00000000 F0.00000000 G0.00000000 H0.00000000 v120.00 a0.000000 b0.000000 c0.000000 d0.000000 e0.000000 g0.000000 t0.000000
First sentence means: Convertion from string "0.000000" to type 'Double' is not correct.

Settings are:
FOV - 62 no opt.
distortion: b - 0 no opt
pitch - 45 opt
roll - 0 opt

advanced - all 0 and no optimalization.

Changing any value doesn't seem to have any result.

Any idea what's wrong?

PS. I've noticed, that drawing trials does not change min/max/avg values, and fit quality stays N/A. Is it possible that image is made out of too short exposure time photos? (40 x 15s, unfortuantely with aprox 10s brakes between shots)

maxlyons
Posts: 3649
Joined: Fri Jun 20, 2003 8:55 pm
Location: USA
Contact:

Re: Star Tracer optimalization problem["Double" ty

Post by maxlyons » Mon Oct 04, 2010 9:13 am

mikepapa wrote:First sentence means: Convertion from string "0.000000" to type 'Double' is not correct.
Sound like a problem. I'd like to fix this. I wonder if there is a problem with "internationalization"? Do you usually use a "," instead of a "." to indicate a decimal place? What happens if you replace all the "." with "," for the values displayed on the GUI?

Also, can you send me the Star Tracer project file, and a screen shot of Star Tracer's main screen?

It sounds like the optimizer is failing before doing any optimization. This would explain why none of the statistics change...because the optimized values have not changed.


Max

Roll'
Posts: 124
Joined: Thu Jul 16, 2009 5:30 pm
Location: Toulouse, France

Post by Roll' » Mon Dec 27, 2010 7:50 am

I tried StarTracer out yesterday and had the same error. I can't optimize any photo and the software changes the "." by a "," automatically.
Do you want I send you my project file?

Image

Arnaud

Lazac
Posts: 5
Joined: Tue Jan 14, 2014 3:46 am

Re: Star Tracer optimalization problem["Double" type c

Post by Lazac » Tue Jan 14, 2014 5:01 am

Hello!

I've got the same issue. :( Doesn't matter what I do, how much lines I add, the optimizer always gives me this error.
mikepapa wrote:I just downloaded Star Tracer, and when I try to use optimalization, I get following results:

02:11:54 Starting process
02:11:54 Process returned: 0
02:11:55 Parsing script
02:11:55 Error 13:Konwersja z ciągu "0.000000" na typ 'Double' nie jest prawidłowa. parsing line: o f0 y0.000000 p7.692514 r43.465762 A0.00000000 B0.00000000 C0.00000000 D0.00000000 E0.00000000 F0.00000000 G0.00000000 H0.00000000 v120.00 a0.000000 b0.000000 c0.000000 d0.000000 e0.000000 g0.000000 t0.000000
First sentence means: Convertion from string "0.000000" to type 'Double' is not correct.

Settings are:
FOV - 62 no opt.
distortion: b - 0 no opt
pitch - 45 opt
roll - 0 opt

advanced - all 0 and no optimalization.

Changing any value doesn't seem to have any result.
I'll send you the file, a screenshot, and the project too. It doesn't matter what picture I use, it still gives the same error.

maxlyons
Posts: 3649
Joined: Fri Jun 20, 2003 8:55 pm
Location: USA
Contact:

Re: Star Tracer optimalization problem["Double" type c

Post by maxlyons » Tue Jan 14, 2014 9:46 am

Thanks...I'm pretty sure this is related to the way different systems use either the "," or the "." as the decimal separator. I'll investigate some more; if I send you a different version of Star Tracer, can you test it on your system?

Thanks,

Max

Lazac
Posts: 5
Joined: Tue Jan 14, 2014 3:46 am

Re: Star Tracer optimalization problem["Double" type c

Post by Lazac » Tue Jan 14, 2014 3:17 pm

Sure thing Max, no problem. :)

maxlyons
Posts: 3649
Joined: Fri Jun 20, 2003 8:55 pm
Location: USA
Contact:

Re: Star Tracer optimalization problem["Double" type c

Post by maxlyons » Thu Jan 16, 2014 10:34 am

I'll work on a fix, and send you something in the next couple of days.

Max

Lazac
Posts: 5
Joined: Tue Jan 14, 2014 3:46 am

Re: Star Tracer optimalization problem["Double" type c

Post by Lazac » Thu Jan 16, 2014 5:10 pm

Thanks in advance, Max!

maxlyons
Posts: 3649
Joined: Fri Jun 20, 2003 8:55 pm
Location: USA
Contact:

Re: Star Tracer optimalization problem["Double" type c

Post by maxlyons » Sat Jan 18, 2014 5:55 pm

I have posted a test version of StarTracer that I hope should help resolve this problem. Can you give it a test a let me know how it works?

http://www.tawbaware.com/startracer_111_beta.zip

Thanks,

Max

Lazac
Posts: 5
Joined: Tue Jan 14, 2014 3:46 am

Re: Star Tracer optimalization problem["Double" type c

Post by Lazac » Mon Jan 20, 2014 2:30 pm

Thanks for the update Max! Unfortunately it didn't work, I'm still getting the same kind of error. I'm starting to think, that maybe it has a problem with the image itself, because it's stacked and so doesn't have the original EXIF data. I'll try to create a single (maybe 60 second exposure) photo, and I'll try it directly with that image. Also I'll try to search the net and download some ther photos, and of course I'll try it out on another computer as well.

I'll post an update about it as soon as I'm done. Cheers!

maxlyons
Posts: 3649
Joined: Fri Jun 20, 2003 8:55 pm
Location: USA
Contact:

Re: Star Tracer optimalization problem["Double" type c

Post by maxlyons » Mon Jan 20, 2014 4:44 pm

Lazac wrote:I'm starting to think, that maybe it has a problem with the image itself, because it's stacked and so doesn't have the original EXIF data.
I don't think this is likely, but I appreciate the testing!

I still think that there is an internationalization issue regarding the use of "," or "." as the decimal separator. Specifically, I think that the output file written by PTAStitcher (the command line application that does the project optimization) is not being understood by StarTracer (the GUI application that the user sees and interacts with). I think this is the cause of the error message about "Error 13...parsing line: o". Behind the scenes there is a lot of communication going on between these two programs and if they have different ideas about whether 1/2 should be represented as "0,5" or "0.5", then problems can happen.

I have posted another beta version with some more changes. Would you mind giving this one a test as well?

Thanks,

Max

Lazac
Posts: 5
Joined: Tue Jan 14, 2014 3:46 am

Re: Star Tracer optimalization problem["Double" type c

Post by Lazac » Thu Jan 23, 2014 11:00 am

Max, you are a genius!

This new version works perfectly. I just made a quick test with it, so the outcome wasn't perfect, but the main thing is, that the issue with the previous error is gone. I mapped about 5-6 startrails, checked the settings (everything was on 0) and then clicked on 'optimize', and voilá, it started doing its job. :) So thanks in advance for your hard work and time! Keep up the good work!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest