前のトピックを表示 :: 次のトピックを表示 |
投稿者 |
メッセージ |
SonotaCo Site Admin
登録日: 2004.08.07 記事: 12669 所在地: 139.67E 35.65N
|
|
トップに戻る |
|
|
Robert J Cobain
登録日: 2006.04.25 記事: 79
|
日時: Tue Jan 30, 2007 5:57 pm 記事の件名: |
|
|
Hi SonotaCo,
Many thanks for this new version, so far I have found it to be very good But I have found a bug in the selection cursor. This bug used to be in UFOA 1 ! Basically in order to be able to click accurately on the stars, for creating manual links, you need to turn off Windows XP themes and return to 'Windows Classic' theme. Otherwise when you click on a star, the selection point will be off target by about 25 pixels.
I will write up a brief 'getting started' with UFOA2 soon.
Magnitude estimates seem to be much better! Thanks, Robert. |
|
トップに戻る |
|
|
SonotaCo Site Admin
登録日: 2004.08.07 記事: 12669 所在地: 139.67E 35.65N
|
日時: Tue Jan 30, 2007 8:21 pm 記事の件名: |
|
|
Robert J Cobain wrote: | Hi SonotaCo,
Many thanks for this new version, so far I have found it to be very good But I have found a bug in the selection cursor. This bug used to be in UFOA 1 ! Basically in order to be able to click accurately on the stars, for creating manual links, you need to turn off Windows XP themes and return to 'Windows Classic' theme. Otherwise when you click on a star, the selection point will be off target by about 25 pixels.
I will write up a brief 'getting started' with UFOA2 soon.
Magnitude estimates seem to be much better! Thanks, Robert. |
Oh!! thank you for using and reporting.
I am just fixing this bug right now
I will release V2.01 tomorrow. |
|
トップに戻る |
|
|
SonotaCo Site Admin
登録日: 2004.08.07 記事: 12669 所在地: 139.67E 35.65N
|
|
トップに戻る |
|
|
SonotaCo Site Admin
登録日: 2004.08.07 記事: 12669 所在地: 139.67E 35.65N
|
日時: Thu Feb 01, 2007 9:35 am 記事の件名: UFOAnalyzerV2 V2.02 was released. |
|
|
UFOAnalyzerV2 V2.02 was released.
All known problems are fixed.
Sorry for frequent updates. |
|
トップに戻る |
|
|
Robert J Cobain
登録日: 2006.04.25 記事: 79
|
日時: Mon Apr 02, 2007 11:20 pm 記事の件名: |
|
|
Hi SonotaCo,
I have been busy re-analyzing all my meteors with UA2 and I think that UA2 is a huge improvement, well done!!
I have just come across a few very small problems.
In the *A.xml file minMag occurs as mimMag
In the UA2Manual page 45 it says that
Quote: | Errm d pixel maximum magnitude measuement error |
Should not Errm be f ? floating point?
Also, sometimes there is a value called SN, what is this?
Robert. |
|
トップに戻る |
|
|
SonotaCo Site Admin
登録日: 2004.08.07 記事: 12669 所在地: 139.67E 35.65N
|
日時: Tue Apr 03, 2007 10:04 am 記事の件名: |
|
|
Robert J Cobain wrote: | Hi SonotaCo,
I have been busy re-analyzing all my meteors with UA2 and I think that UA2 is a huge improvement, well done!!
I have just come across a few very small problems.
In the *A.xml file minMag occurs as mimMag
In the UA2Manual page 45 it says that
Quote: | Errm d pixel maximum magnitude measuement error |
Should not Errm be f ? floating point?
Also, sometimes there is a value called SN, what is this?
Robert. |
Hi Robert
Thank you very much for cooperation.
I did not expect that I can get such helps from overseas. I am very much encouraged.
Sorry there are some inappropriate parameter names and wrong explanations.
"minMag" in *A.xml is not minimum magnitude of observed stars. It is one parameter that corresponds to "magL" in the dialog.
There are 4 parameters that concern the determination of magnitude.
maxLev = levH
maxMag = magH
minLev = levL
minMag = magL
minLev(levL) and minMag(magL) determines one point, and maxLev(levH) maxMag(magH) determines the other point.
Two points determines one straight line on the relation between magnitude and log10 of light sum.
There are two cautions.
minMag(magL) have another meaning. All stars that is dimmer than minMag(magL) will be ignored in the computation of the line(line fitting of least square method). This parameter should be assigned manually according to the situation to avoid the effect of very dim stars that have big errors.
Also, maxLev(levH) should be assigned manually. It must be equal to brightness saturation level of the system. It is usually 255, but there are some system that has 235 or 250 as its maximum. This is decided by device driver of capture the equipment.
Other two parameters are decided by the line fitting.
Errm is floating point. Yes, you are right.
sN is the number of samples(field or frame) that are actually measured.
fN is the number of filed or frame that corresponds to the duration of time.
For example, when fN=11 and sN=8 and 50 filed/second, the duration time is 0.20 second, and there are three fields in the duration time that the objects could not be found in it (leaped). This value will be used in the quality control of future UFOOrbit. |
|
トップに戻る |
|
|
|