> Have gotten back to have another play with my Metrec setup. When I > first started it up with the V4.1 installation, it was working OK but > after installing V5 for DOS, the hardware error is back. It don't > think it is related to the upgrade - this 'on and off' behaviour has > been there before.
did you try different programs that are grabbing images?
grab -2 -pal test.bmp
grabstrm -2 -pal test
lightcrv -2 -pal test.out
metrec metrec.cfg metrec.log
Do they all show the same behaviour?
I can also upload you the full MIL Lite CD that contain the Matrox software Intellicam. You can run that under Win98 to check whether it allows you to grab images. Alternatively, you may send me your grabber and I can test it with my own computer.
> For whatever reason, my config.sys file is empty ... nothing at all > in it. I assume there is only one config.sys and that it is in the > drive root directory. Is that appropriate under a Win98 > installation?
Yes, that's fine. This is my config.sys (with German settings):
>> We don't use Posture, but I've tried the equivalent sort of filters and find
>> that they tend to cause some loss of real data as well.
>
> That is indeed the case - but hey: If we record 20,000 meteors a month, it's
ok if we miss 50 because of automated filters ...
It's always a tradoff between purity and completeness. You have to
decide what's more important. Here's it's purity.
Malcolm
Hi Sirko,
Have gotten back to have another play with my Metrec setup. When I
first started it up with the V4.1 installation, it was working OK but
after installing V5 for DOS, the hardware error is back. It don't
think it is related to the upgrade - this 'on and off' behaviour has
been there before.
For whatever reason, my config.sys file is empty ... nothing at all
in it. I assume there is only one config.sys and that it is in the
drive root directory. Is that appropriate under a Win98
installation?
Not sure where to look next?
Thanks,
Steve Kerr.
>
>
> Steve,
>
> > I have been working on V4.1. I assume that the Readme file is
> unchanged from V5 for DOS and that I don't need to change drivers for
> the Matrox card? I will give that a try.
> the readme file is not yet adapted for V.5, but there only minor
> deviations. There are two or three new parameters, which you will
> find in the corresponding CFG file. The driver is the same.
>
> Best,
> Sirko
>
> --
> ************************************************************
> * Sirko Molau * *
> * Abenstalstr. 13b * __ *
> * D-84072 Seysdorf * " 2B v 2B " *
> * Germany * *
> * phone: +49-8752-869437 * Shakespeare *
> * email: sirko@... * *
> * www : www.molau.de * *
> ************************************************************
>
>
> The worst problem with false alarms comes from clouds when we have a moon. > The second class comes from aircraft, which are a problem for cameras in > areas like Denver (not so much for rural cameras).
ok, these are most tricky indeed, and I did not yet have a good idea how to identify them. The only good thing is that these typically cause "only" a thousand false detections, where sky beamers managed already to create more than 10.000. :-(
> We don't use Posture, but I've tried the equivalent sort of filters and find > that they tend to cause some loss of real data as well.
That is indeed the case - but hey: If we record 20,000 meteors a month, it's ok if we miss 50 because of automated filters ...
Thanks, I might be able to use those.
The worst problem with false alarms comes from clouds when we have a moon.
The second class comes from aircraft, which are a problem for cameras in
areas like Denver (not so much for rural cameras).
I'm looking at identifying clouds by their property of usually generating
events that are physically huge- covering hundreds or thousands of pixels,
but which are also very short- just a few frames. Aircraft I should be able
to filter by noting the way they usually generate multiple events in close
succession, with a small shift in position between them.
We don't use Posture, but I've tried the equivalent sort of filters and find
that they tend to cause some loss of real data as well.
Chris
*****************************************
Chris L Peterson
Cloudbait Observatory
http://www.cloudbait.com
----- Original Message -----
From: "Sirko Molau" <sirko@...>
To: <metrec@yahoogroups.com>
Sent: Thursday, December 03, 2009 2:36 PM
Subject: Re: [MetRec] Meaning of a couple logged terms
Hi Chris,
> There are two values in the log file which I'd wondering the meaning of.
> The
> first is 'pixel' and the second is 'å' (the third and sixth items given
> after the meteor frame coordinates). I've always ignored these, but I'm
> exploring ways of automating false alarm detection during post processing
> (on some cameras we get 1000 false events per night) and trying to use
> these
> additional terms to produce a filter of some sort.
these are internal parameters during the detection process which reflect how
well the meteor was recorded. Pixel stands for "number of pixels above the
detection threshold (at maximum)" - the more pixels, the higher the chance
to have a real object. The second parameter (which should be a sigma, but
may be listed as another special character if you used a different char set)
tells you how many times the object was above the current detection
threshold (at maximum). 1.0 means it was just at the threshold, 2.0 means it
was twice the threshold, etc. Again, the larger the value, the more obviuos
the object.
Best,
Sirko
PS: What kind of false detections do you get? There are a number of PostProc
command line parameters that help you in these cases. A typical problem are
sky beamers with low clouds, for example. The will cause a number of false
detections in short succession as the beam crosses the fov. In this case, I
typically run first a postproc -maxcount 3 to delete typically 50-70% of the
false detections.
> There are two values in the log file which I'd wondering the meaning of. The > first is 'pixel' and the second is 'å' (the third and sixth items given > after the meteor frame coordinates). I've always ignored these, but I'm > exploring ways of automating false alarm detection during post processing > (on some cameras we get 1000 false events per night) and trying to use these > additional terms to produce a filter of some sort.
these are internal parameters during the detection process which reflect how well the meteor was recorded. Pixel stands for "number of pixels above the detection threshold (at maximum)" - the more pixels, the higher the chance to have a real object. The second parameter (which should be a sigma, but may be listed as another special character if you used a different char set) tells you how many times the object was above the current detection threshold (at maximum). 1.0 means it was just at the threshold, 2.0 means it was twice the threshold, etc. Again, the larger the value, the more obviuos the object.
Best,
Sirko
PS: What kind of false detections do you get? There are a number of PostProc command line parameters that help you in these cases. A typical problem are sky beamers with low clouds, for example. The will cause a number of false detections in short succession as the beam crosses the fov. In this case, I typically run first a postproc -maxcount 3 to delete typically 50-70% of the false detections.
> i am mainly on the look out for a good camera as the ones i have been playing with are not up to the job, if you could point me in the right direction that would be appreciated.
there are just two types of cameras used by 90% of all meteor observers - the current model names are Mintron 12V6-EX and the Watec 902H2 Ultimate. They cost typically around 300 Euro. Just recently (Noc 23) there was a posting from Stefan Blöchl for a direct purchase of the Watec from the manufacturer at special conditions. Just ahve a look at the mailing list archive.
many thanks for your reply , i am keeping a eye on a card on ebay at the moment , its got till weekend so will let you know if i get that , thanks again for the offer.
i am mainly on the look out for a good camera as the ones i have been playing with are not up to the job, if you could point me in the right direction that would be appreciated.
i wonder if you know anyone in the group if they saw the large meteor / fireball on the 26/11/09 at approx 17.58 ( i am in the center of the uk , in the city of leicester about 100 miles north of london)
currently MetRec does not support this grabber, as I'm using MIL Lite 7.5 for Win and 6.01 for Dos, but the Morphis is only supported from MIL 8.0 onwards.
Given that I get 8.0 somewhere for free I may test at some time to support this grabber. If I were you, however, I wouldn't wait for that day. ;-)
I recently sold 4 Matrox Meteor II to Javor at 65 Euro each, so currently I have none here. It usually takes a few weeks to get one at such a rate, so chances are ~50/50 that I get one more before Christmas. I'll reserve it for you if you like.
a little introduction , i been interested in astronomy and meteors since i was a kid and now found metrec, i had a go at using tv cards and cctv software but no luck,
i seen the software works on the matrox meteor cards , but wondering if it works on the Matrox Morphis MOR/2VD-Frame Grabber card as there some on ebay for £15 + postage
if not , anyone know where to get a meteor card at a resonable price
cheers matt
------------------------------------
------------------------------------------------------------------------ MetRec Homepage: http://www.metrec.org MetRec Download sites: http://www.metrec.org/download http://ftp.imo.net/pub/software/metrec ------------------------------------------------------------------------ To unsubscribe from the MetRec info list, send a blank message to metrec-unsubscribe@groups.yahoo.com, or visit groups.yahoo.com/group/metrec -----------------------------------------------------------------------Yahoo! Groups Links
No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.426 / Virus Database: 270.14.87/2536 - Release Date: 11/30/09 07:31:00
There are two values in the log file which I'd wondering the meaning of. The
first is 'pixel' and the second is 'å' (the third and sixth items given
after the meteor frame coordinates). I've always ignored these, but I'm
exploring ways of automating false alarm detection during post processing
(on some cameras we get 1000 false events per night) and trying to use these
additional terms to produce a filter of some sort.
Chris
*****************************************
Chris L Peterson
Cloudbait Observatory
http://www.cloudbait.com
> I have been working on V4.1. I assume that the Readme file is unchanged from V5 for DOS and that I don't need to change drivers for the Matrox card? I will give that a try.
the readme file is not yet adapted for V.5, but there only minor deviations. There are two or three new parameters, which you will find in the corresponding CFG file. The driver is the same.
Hi Sirko,
Thanks for the reply. It might be quite a few days before I get back to try
some of these fixes.
>
> Which version of MetRec are you using: Version 4 or the new beta version
> 5? I would suggest you to donwload the later one, which runs already
> quite stable.
>
I have been working on V4.1. I assume that the Readme file is unchanged from
V5 for DOS and that I don't need to change drivers for the Matrox card? I will
give that a try.
> How do you run grab: Do you boot Win98 and try to run grab in a DOS box,
> or do you restart Win98 in DOS mode? I would suggest not to boot Win98
> at all after you installed the driver, but run MetRec directly from the
> DOS prompt. The readme file tells you how to achieve this.
>
I have been restarting the machine in DOS as you suggest.
> Did you check that the is no emm386 in your config.sys?
>
Ah! I saw that in the Readme file but didn't know enough about computers to
know to look in config.sys. I will check this one out.
Thanks again,
Steve Kerr.
> ---------- Forwarded message ----------
> From: Denis Denisenko <denis@...>
> Date: 2009/11/26
> Subject: (meteorobs) Important! Check your Leonids images of Nov. 15-18
> To: Meteor Observing Mailing List <meteorobs@...>
>
>
> Dear meteor observers!
>
> Possible Nova in Eridanus was discovered by famous Japanese astronomer
> Koichi Itagaki on Nov. 25.536 UT (CBET 2050) at magnitude 8.1. It was
> then retrospectively found on ASAS images dated by as early as Nov.
> 19.241 UT being yet brighter at 7.3 mag (AAVSO Special Notice #181).
> The star has 15th magnitude at quiescence.
>
> No images of possible Nova Eridani are available between Nov. 10.236 UT
> when it was fainter than 14.0 and Nov. 19.241 UT. Looks like the real
> maximum has been missed! Since the spectrum of the star in outburst
> shows bright Balmer emission lines with expansion velocity of 3400-3600
> km/s, this object is likely a classical Nova rather than a cataclysmic
> variable of WZ Sge type. This means that the real outburst amplitude
> should have been 13-14 magnitudes rather than the observed 7.5, and some
> time between Nov. 10th and 19th it *could* have been as bright as mag
> 1-2!!! But nobody knows it for sure. Not yet!
>
> Here is where your help is needed. Please check your photos (and
> probably even videos) from the nights of 2009 Leonid shower activity
> containing Orion and its surrounding constellations. The Nova is
> located near the Orion-Eridanus border, about 7 deg West and 2 deg South
> of Rigel. Precise coordinates of the star are:
>
> R.A. = 04h47m54.2s, Decl. = -10d10'43" (J2000.0)
>
> The position of star is shown with blue dashes on the following chart
> (stars to 6.5m are shown):
>
>
http://hea.iki.rssi.ru/~denis/NovaEri2009Nov18.gif<http://hea.iki.rssi.ru/%7Eden\
is/NovaEri2009Nov18.gif>
>
> If you find the images taken any time between Nov. 10 and Nov. 19
> covering the area of interest, please check them for the presence of the
> Nova Eridani 2009, or send them directly to me for the analysis and
> photometry via E-mail address below in my signature. Also, feel free to
> send this message to other mailing list and circulate it among your
> fellow astronomers. This is really a rare coincidence that many images
> of the sky were taken just in time during the Nova outburst because of
> the Leonid meteors activity, and reconstructing the light curve of this
> variable star would be very important.
>
> Best regards,
>
> Denis
> --
> Denis V. Denisenko
> Space Research Institute
> Profsoyuznaya st., 84/32
> 117997, Moscow, Russia
> denis@...
> _______________________________________________
> Mailing list meteorobs: meteorobs@...
> To UNSUBSCRIBE, email: owner-meteorobs@...
> http://lists.meteorobs.org/mailman/listinfo/meteorobs
>
currently MetRec does not support this grabber, as I'm using MIL Lite 7.5 for Win and 6.01 for Dos, but the Morphis is only supported from MIL 8.0 onwards.
Given that I get 8.0 somewhere for free I may test at some time to support this grabber. If I were you, however, I wouldn't wait for that day. ;-)
I recently sold 4 Matrox Meteor II to Javor at 65 Euro each, so currently I have none here. It usually takes a few weeks to get one at such a rate, so chances are ~50/50 that I get one more before Christmas. I'll reserve it for you if you like.
a little introduction , i been interested in astronomy and meteors since i was a kid and now found metrec, i had a go at using tv cards and cctv software but no luck,
i seen the software works on the matrox meteor cards , but wondering if it works on the Matrox Morphis MOR/2VD-Frame Grabber card as there some on ebay for £15 + postage
if not , anyone know where to get a meteor card at a resonable price
cheers matt
------------------------------------
------------------------------------------------------------------------ MetRec Homepage: http://www.metrec.org MetRec Download sites: http://www.metrec.org/download http://ftp.imo.net/pub/software/metrec ------------------------------------------------------------------------ To unsubscribe from the MetRec info list, send a blank message to metrec-unsubscribe@..., or visit groups.yahoo.com/group/metrec -----------------------------------------------------------------------Yahoo! Groups Links
the error message you get sounds indeed like a hardware error, but I would not link it directly to the framegrabber.
Which version of MetRec are you using: Version 4 or the new beta version 5? I would suggest you to donwload the later one, which runs already quite stable.
How do you run grab: Do you boot Win98 and try to run grab in a DOS box, or do you restart Win98 in DOS mode? I would suggest not to boot Win98 at all after you installed the driver, but run MetRec directly from the DOS prompt. The readme file tells you how to achieve this.
Did you check that the is no emm386 in your config.sys?
Please let me know about the results, and we'll hopefully find a solution.
> Hi, > > After many years of working towards it, I am getting close to commissioning my Metrec setup. One of the delays has been around a mystery error that had made running the grab.exe impossible. This evening, grab.exe starting working again so I have now realised that the error comes and goes with no obvious connection with anything else. The error text doesn't help me much although the mention of 'device not available' is suggesting that it might be hardware related to the Matrox card. If anyone can help me with trying to resolve this, it would be very much appreciated. > > The text that appears after invoking the Grab.exe is ... > > DOS/4GW Protected Mode Run-time Version 1.97 > Copyright (C) Rational Systems, Inc. 1990-94 > DOS/4GW Error (2001): exception 07h (device not available) at 150:001C2C50 > TSF32: prev_tsf32 5278 > SS 158 DS 158 ES 158 FS 0 GS 20 > EAX 3FECDA EBX 3FECD8 ECX 4000 EDX 42FF01 > ESI 3FED2C EDI 3FFEG0 EBP 0 ESP 427E1C > CS:IP 150:001C2C50 ID 07 COD 3FECDA FLG 10202 > CS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF9B > SS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93 > DS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93 > ES= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93 > FS= 0, USE16, byte granular, limit 0, base 14, acc 0 > GS= 20, USE16, byte granular, limit FFFF, base 8F50, acc93 > CRO:PG:0 ET:1 TS:1 EM:0 MP:1 PE:1 CR2:F6145EBF CR3:0 > Crash Address (unrelocated) =1:0002CC50 > > The PC is a Pentium III running Win 98SE > > Any help with this would be very much appreciated. > Thanks, > Steve Kerr. > > > > ------------------------------------ > > ------------------------------------------------------------------------ > MetRec Homepage: http://www.metrec.org > MetRec Download sites: > http://www.metrec.org/download > http://ftp.imo.net/pub/software/metrec > ------------------------------------------------------------------------ > To unsubscribe from the MetRec info list, send a blank message to > metrec-unsubscribe@..., or visit groups.yahoo.com/group/metrec > -----------------------------------------------------------------------Yahoo! Groups Links > > <*> To visit your group on the web, go to: > http://groups.yahoo.com/group/metrec/ > > <*> Your email settings: > Individual Email | Traditional > > <*> To change settings online go to: > http://groups.yahoo.com/group/metrec/join > (Yahoo! ID required) > > <*> To change settings via email: > metrec-digest@yahoogroups.com > metrec-fullfeatured@yahoogroups.com > > <*> To unsubscribe from this group, send an email to: > metrec-unsubscribe@yahoogroups.com > > <*> Your use of Yahoo! Groups is subject to: > http://docs.yahoo.com/info/terms/ >
hi everyone
a little introduction , i been interested in astronomy and meteors since i was a
kid and now found metrec, i had a go at using tv cards and cctv software but no
luck,
i seen the software works on the matrox meteor cards , but wondering if it works
on the Matrox Morphis MOR/2VD-Frame Grabber card as there some on ebay for £15 +
postage
if not , anyone know where to get a meteor card at a resonable price
cheers matt
Hi,
After many years of working towards it, I am getting close to commissioning my
Metrec setup. One of the delays has been around a mystery error that had made
running the grab.exe impossible. This evening, grab.exe starting working again
so I have now realised that the error comes and goes with no obvious connection
with anything else. The error text doesn't help me much although the mention of
'device not available' is suggesting that it might be hardware related to the
Matrox card. If anyone can help me with trying to resolve this, it would be
very much appreciated.
The text that appears after invoking the Grab.exe is ...
DOS/4GW Protected Mode Run-time Version 1.97
Copyright (C) Rational Systems, Inc. 1990-94
DOS/4GW Error (2001): exception 07h (device not available) at 150:001C2C50
TSF32: prev_tsf32 5278
SS 158 DS 158 ES 158 FS 0 GS 20
EAX 3FECDA EBX 3FECD8 ECX 4000 EDX 42FF01
ESI 3FED2C EDI 3FFEG0 EBP 0 ESP 427E1C
CS:IP 150:001C2C50 ID 07 COD 3FECDA FLG 10202
CS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF9B
SS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93
DS= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93
ES= 150, USE32, page granular, limit FFFFFFFF, base 0, accGF93
FS= 0, USE16, byte granular, limit 0, base 14, acc 0
GS= 20, USE16, byte granular, limit FFFF, base 8F50, acc93
CRO:PG:0 ET:1 TS:1 EM:0 MP:1 PE:1 CR2:F6145EBF CR3:0
Crash Address (unrelocated) =1:0002CC50
The PC is a Pentium III running Win 98SE
Any help with this would be very much appreciated.
Thanks,
Steve Kerr.
some time ago I gave Sirko a visit and we had talked about suitable cameras for Meteor Observations.
I had sent a request to a good friend of mine. Today he had informed me about the retail price on "WAT-902H2 Ultimate" cameras as direct purchase from the manufacturer.
If enough out there are interested, then the price will be approx. 250 Euros or less incl. shipping and customs/tax (shipping to me).
You could pic up "your" cam at my QTH or add approx. 10Euros for additional shipping costs.
If someone out there is interested in such a camera, then please let me know until December 10th.
73
Stefan
_____________________________
Did you know:
Radio astronomers do it day and night :)
__________________________________________________ Do You Yahoo!? Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails. http://mail.yahoo.com
no, there is no automated way to modify the date. It's alos not sufficient to rename the dir, because a wrong date will result in wrong coordinates (remember that the difference between solar and sideral time is about 4 mins per day). I have some scripts to correct the coordinates, so just upload the data and tell me what needs to be corrected.
Hi.
Few days ago I had to reset BIOS. I changed time, but I forgot to change date,
so date in log file is wrong and name of the directory, where are stored bmp
pictures for each meteor, is wrong too. Is possible to change date and name of
directory with postproc or I have to change them manually?
CS, Mitja
today I updated the MetRec 5 (beta) binaries at http://www.metrec.org/download. The following issues were fixed:
DOS:
* the determination of the recognition time is working properly now
* a missing video signal is correctly recognized
DOS & WIN:
* the time stamp function -ts works now also with grabseq
* PostProc got a new parameter -noint. It allows you to run it non-interactively, i.e. the commands you listed at the command line (e.g. -maxcount x, -shower or -ref) will be executed automatically without interaction. So you can run PostProc in batch mode now.
* PostProc -shower will always save the logfile no matter whether the meteor shower assignment of individual meteors changed or not
* when a ref file is configured with a path (e.g. ..\dummy.ref), it will still be copied to the data directory when MetRec quits (even though I do not recommend this)
* a minor bug with the -nosync and -noflash options of PostProc is fixed
Known issues not yet fixed:
* MetRec.com is not available for Windows, so you cannot configure AutoRestart = yes
Feel free to continue testing MetRec 5 for DOS as well.
Hi Antal, My colleague uses a Tamron 4-12mm F1.2. I focused it, it has a nice sharp image, better than 8mm at my 8-48mm F1.2 which has some abberations on stars and streetlights. But there is noticably darker (hence lower S/N ratio, less good for capturing very faint events) if you compare to a F<1.0 prime. This lens also exhibits large barrel distortion at the wider angles, I don't know if this is anymore controlled with other lenses. I don't remember how strong light falloff was, so it must have been very acceptable.
after several month of continous search process I have found only two potential alternatives for Computar 3,6mm /f0.8 lens, which is not in production any more. (Probably I ordered the last demo piece from Japan in April....)
The result is quite poor:
- A412ASIR varifocal 4-12mm / f1.2 from TAMRON (about 138 EUR with VAT)
- H3Z4512CS-IR 4.5-12mm / f1.2 from Computar (about 226 EUR with VAT)
Normally price and quality comes together.
Still I would like to ask your experience or just youur opinion with this lenses before ordering.
I observed a seriuos bug in the DOS version of MetRec 5.0. The timer is not properly working, an issue that I observed and fixed before, but that somehow occured again now. I won't be able to fix this on short notice, so please use the old version until notified.
Best,
Sirko
PS: The Windows version should not be affected, but you should pay special attention to the recognition time, anyway.
more than a year ago, Hans Smit from ESA has started to work on a Windows port of MetRec. Since early 2009, both of us continued to work intensively on the task to create a joint code base for Dos and Windows and make all function of MetRec available under Windows. OS specific functions were moved to separate files, some core routines underwent a significant redesign and simplification, and a number of bugs (mainly memory violations) that went unnoticed under DOS were identified and removed. In parallel, some new function were implemented:
* Grab/GrabSeq/GrabStrm: date & time stamp can be inserted * MetRec: a background image may be saved after a predefined amount of time; DST correction * Ref2Txt & Txt2Kml: create KML files from REF files in a comfortable way * RadFind & StrmFind: implementation of the new radiant and meteor shower search algorithm (observability function, Laplace distribution, recomputed meteor shower assignment, meteor altitude formula); shower identification based on the MDC working list with >300 showers * RefStars: combined measurement of several reference images * MetRec, PostProc & Co: extension of PosDat header IDs 000-ZZZ, the frame grabber device number can be chosen if more than one grabber is installed (not yet fully tested)
Overall, there were about 20 code iterations this year, and all but a few functions (e.g. support of DCF clocks) are available now under Windows as well. Beside our dry runs, the software was continuously tested on Win XP in the field by Detlef Koschny and some Polish observers. Now we believe that it is stable enough to be tested by other observers as well. You can download the beta versions from
Beside the new features, nothing has changed for the DOS version.
For the Windows version you find a file driverxp.zip. To install the Meteor II grabber under XP, unpack this file into some temp directory and start install.bat. More details are given in the readme.txt file of the same directory. The driver is striped down from the original MIL Lite 7.5 redistribution. I removed unnecessary files to reduce the overall size from 300 to 15 MB. If you encounter any problem with the reduced version, please, let me know.
The MetRec 5.0 configuration file metrec.cfg contains three new parameters and one whose range has changed:
* FrameGrabberDeviceNumber
* DSTCorrection
* SaveBackgroundRate
* ClockSyncRate
For details, please refer to the description in the sample configuration file.
The parameter FrameStackCount is not supported anymore.
Remember that the software has still beta status, so do not let it run unattended for many days or weeks, but check the results frequently to ensure everything is running properly. If you observe strange behaviour, missing functions or if you run into bugs, please let Hans and me know. If you gain experiences with Windows (e.g. you should turn off automated software updates so that they do not interfer with MetRec), please, let us know as well so that we can compile a best practice guide.
Best wishes,
Sirko
PS: The readme.txt file and the screenshots have not been updated yet.
Hi Sebastià,
the IR tag is a bit tricky and mainly depends on the manufacturer. As it
is known the refractive index changes with the wavelenght. In optics the
results is achromatism or chromatic aberration, which means that the
focus of the different colours are not in the same point (as desired).
Many of the cameras that we use have some IR sensitivity which results
in an non-visual achromatism. It is usually seen in good visual
telescopes, impossible to be focused when using an IR-enhanced CCD.
Manufacturers give two solutions for this "problem":
- cheap: IR night lenses, that focuses the best close to the
IR. The focus is only shifted towards IR.
- expensive: IR day-night lenses, that focuses all the wavelenghts
from blue to almost the micron. This solution needs more lenses (or
better ones) that the previous solution (like the achromatic triplets
for the eyepieces).
Aspheric means that some of its elements have surfaces different from
the spherical ones. These elements are more expensive but can correct
many aberrations. They usually replace groups of several elements.
So, in conclusion, are IR aspherical lenses the best choice? Not sure.
We need to test it. Actually, the quality of the lenses depends on other
parameters appart from these, so it is not easy to choose the best lens.
Some time ago, a paper about it appeared in WGN, but I think many of the
lenses studied there are not easy to buy now. Maybe Sirko can help us.
Un saludo,
Paco Ocaña
Sebastià Torrell escribió:
> My experience says they are important high quality lenses instead of
> lenses focal relationship too open.
> For perhaps scenes are good, but not for point objects, as aberrations
> that do not improve the stars, yet it increased the backlight.
>
> My question is, if someone knows exactly what the tags mean IR
> Aspherical lenses and lenses?
>
> un saludo
>
>
> ------------------------------------
>
> ------------------------------------------------------------------------
> MetRec Homepage: http://www.metrec.org
> MetRec Download sites:
> http://www.metrec.org/download
> http://ftp.imo.net/pub/software/metrec
> ------------------------------------------------------------------------
> To unsubscribe from the MetRec info list, send a blank message to
> metrec-unsubscribe@..., or visit groups.yahoo.com/group/metrec
> -----------------------------------------------------------------------Yahoo!
Groups Links
>
>
ok
I allready know these group
waht I try to find is sombody that are active whit your system
and made some allsky survy
jack 47'n 71'W
> You could contact the Quebec Centre of the RASC at: http://
> www.sracquebec.org/
>
>
> On 15-Aug-09, at 11:40 AM, Jacques Savard wrote:
>
> > I live in quebec city canada
> >
> > I have some computer experience
> >
> > and some atm also
> >
> > I plan to built a allsky whit some old webcam and vhs camcorder lens
> >
> > 4.8 mm
> >
> > do some of your meber are near me in quebec or mtl?
> >
> > jack 47'n 71'W
> >
> >
>
I live in quebec city canada
I have some computer experience
and some atm also
I plan to built a allsky whit some old webcam and vhs camcorder lens
4.8 mm
do some of your meber are near me in quebec or mtl?
jack 47'n 71'W
My experience says they are important high quality lenses instead of
lenses focal relationship too open.
For perhaps scenes are good, but not for point objects, as aberrations
that do not improve the stars, yet it increased the backlight.
My question is, if someone knows exactly what the tags mean IR
Aspherical lenses and lenses?
un saludo
Hi list,
I need some lenses for a Watec 902 / 902HS and I don´t know if it need
DC auto-iris or Video Auto-Iris. I already have a Watec 902H and it
needs Video ones, which are not as usual.
Anyone using one of these cameras? Which lens do you use?
Thanks,
Paco Ocaña