(meteorobs) OT -Question to the UFOCaptureV2. -PAUL PUGH et.al.,

[Larry]

Hi Paco.

One of the drawbacks I think is my computer may be TOO fast. I see far too 
many points of light that are NOT stars OR hot pixels. I believe this is due 
to thermal noise in the entire computer system from super fast processing. 
This noise is constantly changing with every "T" image even with near 
simulaneous triggers. This difference was quite noticeable when comparing a 
800 mhz computer, and a 900 mhz computer at the same time with the 2.4Ghz 
computer with the exact same settings on all. It does erase with noise 
removal in software photo programs when processing the .avi image later with 
registax and .avi2Bmp.

I use Avermedia capturing 'cause they were cheap on e-bray. The USB frame 
grabbers are superior from all that I have reviewed. But, with 4 or 5 
Avermedia's in all the computers, it can get too expensive to start changing 
them out until I have selected which "cheaper" one to test.

My hobbies keep my wallet empty. To much spending on non-essentials like 
food and utilities. :-)

I manage the nightly 10 or so Gigabytes with daily removal. I do plan on 
using a spare 60Gb. HDD on either the Sentinel or the 2.4 computer to give 
me some rest in the morning file deleting........

All in all.....I believe UFOV2,22 will be the primary backup from here on. I 
did not even turn on the Handyavi computer last night. I need real images of 
real events too much.

YCSentinel



----- Original Message ----- 
From: "Francisco Ocaña" <albireo3000 at yahoo.es>
To: "Global Meteor Observing Forum" <meteorobs at meteorobs.org>
Sent: 2009/08/28 10:44
Subject: Re: (meteorobs) OT -Question to the UFOCaptureV2. -PAUL PUGH 
et.al.,


Hi,

Larry wrote:
> This
> starting position is excellent for meteor radiants and total meteor counts
> using the "T" image....but not magnitude. The .avi's are flawless.
>
>
Well the UfoAnalyzer tool allows you to determine the magnitude of each
event. This is not easy because you never have more than 20-30
references, most of them saturated or undersampled. Remember that most
of our CCTV cameras have a very tiny dinamic range (30 - 45 dB). If the
fireball is within this range (it does not saturate), UfoA may be able
to determine "accurately" its magnitude. However brighter events are
always wrong estimated.
> (I believe) great care must be excersized on Scintillation Mask and Frame
> shift settings. Both can cause clipping on leading edges & trailing edges 
> of
> a meteors weaker ablation. I understand that frame shift value determines
> how far back in the frames UFO looks in determining a trigger or ending a
> triggered .avi.... (IF) Head & Tail are short values. I will continue to 
> use
> 30 (1 second) on both and examine that function more closely later.
>
30 is ok, but 60 will be too (if you don´t have RAM or HDD
resctrictions. Stacking 120 frames will give you more reference stars (
I think if you double the time you get 0,75 magnitude deeper).
> I will NEVER use Slow Object masking. I need the plane trails and also 
> will
> not risk losing any part of slower fireballs. Another area of further
> investigation....
>
Never say never, jeje. I use plane trails to confirm it works, however
the slowest ever fireball will be faster than 80% of the planes. I have
everyday 15-20 planes crossing the field for more than 25 seconds. That
means 400 seconds or almost 2 Gb of planes.  How do you manage them?
> UFO  uses the same model card without these defects.
>
And about Frame Grabber Cards... which do you (and other UfoCapture
users) use? I use a chip USB one, and I want to upgrade to a PCI one.
Any ideas?

Best,

Paco

_______________________________________________
Mailing list meteorobs: meteorobs at meteorobs.org
To UNSUBSCRIBE, email: owner-meteorobs at meteorobs.org
http://lists.meteorobs.org/mailman/listinfo/meteorobs