Re: trying to find lovejoy
With either .net or .org I get exactly 50 objects. Wish I knew why.
Greg
toggle quoted message
Show quoted text
On 01/01/2015 08:18 PM, allan meyer ameyer@... [xephem] wrote: Replace ".net" with ".org"
Recently updated the file, loads with count 773 entries.
With that update XEphem shows C/2014 Q2 Lovejoy
as currently at about 4:57, -17:05 (J2000, Jan. 2, 1h UT), mag. 5.2
------------------------------------
Posted by: allan meyer <ameyer@...>
------------------------------------
------------------------------------
Yahoo Groups Links
|
Re: trying to find lovejoy
Replace ".net" with ".org"
Recently updated the file, loads with count 773 entries.
With that update XEphem shows C/2014 Q2 Lovejoy
as currently at about 4:57, -17:05 (J2000, Jan. 2, 1h UT), mag. 5.2
|
I dusted off Xephem today trying to figure out where Comet Lovejoy is,
noticed that in the download window that the download location was still
cfa-www.harvard, updated it to be
but after pressing "get" there appear to be only 50 objects, when
just looking at the file manually I would expect more than 700.
Is there something obvious I forgot to do?
|
Hey,
If you want to proceed, lets take this offline.
dxwayne at . We can post summary
results later. To quiesce this particular thread...
I've just noticed some sort of disconnect between the
XEphem built-in Ast...edb files and the 'daily' type
of MPC orbit files. But!!! I am moving fast over this problem.
I downloaded the MPCORB.DAT.gz file and found
the asteroid you seek. However it would need to
be converted to .edb file. The XEphem user doc
describes the fields. The MPCORB.DAT file
is? a 'FORTRAN' like fixed column deal.
I deal with these types of files from Vizier all
the time, using python/editor as my choice approach
for the moment. There is a completely new
technique embedded in astropy for example, that allows
grabbing tabular data and converting to
ds9 tsv files pretty easy.
I downloaded the MPCORB.DAT file. It is big (as in I don't want to hand edit it!) and appears well formed.
The MPC states "At present MPCORB is not
available via anon-ftp on this site."
Not sure what the ramifications for XEphem might be.
I don't know the direct link between the XEphem
download files and this master file. I took Ceres as an example, and could not match the fields up between XEphem doc, edb, and Ceres' line from MPCORB. This is about as far as I can go with this, short of writing
a python script to convert the MPCORB to edb- several
hours at best. I don't have that time in my schedule. I
need to dig into the XEphem source code to understand
the real process. Someone might make a hack that takes the
file you get via the HTTP download and make the
files you need.
So, alas, this first cup of coffee exercise hit the bottom
of the cup before the bottom of the problem. Do I
get partial credit?
This page lets you enter asteroids, and will return
a .edb line for just your target(s) of interest. That
is how I got my little ast.edb file hacked together for
testing, and was able to spot the H issue. H is
in MPCORB.dat.
How well are your python skills?? I suggest to all to use
the Anaconda python package from Continuum.io site.
It is free, and well presented for general analytics
use on all platforms. I've used it under Mac and Linux,
astropy is there and completely integrated. There is
a trick to managing the PYTHONPATH etc to make
it sing. The 'Young Turks' of astronomy are migrating
to iPython (Anaconda is supporting this well)? from IDL.
For astronomy try to stick to the 2.7.6+, as the bulk
of existing stuff is there. Python 3.3.x is OK, but 2.7
seems to be the one for astronomy for now, seems to be
the base for os scripts too.
--W
On Wed, Dec 10, 2014 at 5:50 PM, Santiago Roland santiago@... [xephem] <xephem@...> wrote:
?
So, is this page of any use?
Cheers,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
El 10/12/14 a las 22:04, Wayne Green dxwayne@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
>
>
>
>
> is one place; I checked for your asteroids they are there, maybe
> with a different primary name?
>
> --W
>
>
> On Tue, Dec 9, 2014 at 9:17 AM, Wayne Green <dxwayne@...
> dxwayne@...>> wrote:
>
> Hey,
>
> using xephem 3.7.7-RC3
>
> I checked JPL and the MPC for the object 2010 JT123, for which
> they show an updated name of 2014 FD7.
>
> I don't find either name in the .edb files from Lowell or
> the MPC bright, or dim, even after update.
>
> MPC directly reports the mag as 23.2ish for now.
>
> JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
>
> Can you send me the filename and line from your .edb file?
>
> grep '2014.*FD7' *edb
> and
> grep '2010.*JT123' *edb
>
> I don't get any output for either query. check your install
> base (mine is /usr/local/xephem/catalogs) and from
> your ~/.xephem dir.
>
> During this chase, I deleted files from /usr/share/xephem/catalogs...
> Reran the app.
> Found MPC files in my ~/.xephem directory!
> deleted those
> reloaded
>
>
> So, I asked the MPC for the single line for XEphem, and saved this
> into a file in ~/.xephem/ast.edb and I can find, load, query, and
> Sky Point the 2014*FD7 critter.
>
> The mag reports fine.
>
> # From MPO315289 (HACKED HERE, OK in ast.edb attached)
> 2014 FD7,e,15.4565,187.2564,138.8035
> ,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
>
>
> Attached is the hacked output from a JPL vector query
> with object data from JPL and the hacked table
> from the MPC direct query.
>
> I realize you are not looking for these data exactly, but
> trying to solve the XEphem .edb issue, but here is
> the 'truth' from my two main sources for a baseline
> for debugging.
>
> I don't have a lot of time to dig into the code, but hope this
> helps. Good first cup of coffee exercise for me this AM!
>
>
>
>
>
> --Wayne
>
>
>
> On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland santiago@...
> santiago@...> [xephem] <xephem@...
> xephem@...>> wrote:
>
> __
>
>
> Yeah, i keep having the same problem. I downloaded the Lowell dim
> catalog and magnitudes are fine, The issue is with the MPC files. I
> downloaded them in the orbital elements page for planetarium
> programs,
> fetched the link and entered in the download links in XEphem,
> deleted
> all catalogs and reloaded them several times. I get for unusual,
> magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
> deleted the .edb and generated them again. See object 2010
> JT123, what
> magnitude do you have for this object? I compiled the lastest
> version
> and i'm running it on Debian, XEphem 3.7.6
>
> Best Regards,
>
> Santiago Roland.-
> ---------------------------------
> Jabber: santiago@... santiago@...>
> Diaspora*:
> Identi.ca:
> openPGP ID: 7BE512C5
> openPGP key:
> ---------------------------------
>
> El 21/11/14 a las 15:04, ecdowney@...
> ecdowney@...> [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
> >
> >
> > You do realize that Downloading just stores them on disk,
> right? You
> > must still Load them using Data -> Files.
> >
> >
> >
> >
>
>
>
>
> --
>
>
> -- Wayne
>
>
>
>
> --
>
>
> -- Wayne
>
>
|
So, is this page of any use?
Cheers,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
toggle quoted message
Show quoted text
El 10/12/14 a las 22:04, Wayne Green dxwayne@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
is one place; I checked for your asteroids they are there, maybe
with a different primary name?
--W
On Tue, Dec 9, 2014 at 9:17 AM, Wayne Green <dxwayne@...
<mailto:dxwayne@...>> wrote:
Hey,
using xephem 3.7.7-RC3
I checked JPL and the MPC for the object 2010 JT123, for which
they show an updated name of 2014 FD7.
I don't find either name in the .edb files from Lowell or
the MPC bright, or dim, even after update.
MPC directly reports the mag as 23.2ish for now.
JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
Can you send me the filename and line from your .edb file?
grep '2014.*FD7' *edb
and
grep '2010.*JT123' *edb
I don't get any output for either query. check your install
base (mine is /usr/local/xephem/catalogs) and from
your ~/.xephem dir.
During this chase, I deleted files from /usr/share/xephem/catalogs...
Reran the app.
Found MPC files in my ~/.xephem directory!
deleted those
reloaded
So, I asked the MPC for the single line for XEphem, and saved this
into a file in ~/.xephem/ast.edb and I can find, load, query, and
Sky Point the 2014*FD7 critter.
The mag reports fine.
# From MPO315289 (HACKED HERE, OK in ast.edb attached)
2014 FD7,e,15.4565,187.2564,138.8035
,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
Attached is the hacked output from a JPL vector query
with object data from JPL and the hacked table
from the MPC direct query.
I realize you are not looking for these data exactly, but
trying to solve the XEphem .edb issue, but here is
the 'truth' from my two main sources for a baseline
for debugging.
I don't have a lot of time to dig into the code, but hope this
helps. Good first cup of coffee exercise for me this AM!
--Wayne
On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland santiago@...
<mailto:santiago@...> [xephem] <xephem@...
<mailto:xephem@...>> wrote:
__
Yeah, i keep having the same problem. I downloaded the Lowell dim
catalog and magnitudes are fine, The issue is with the MPC files. I
downloaded them in the orbital elements page for planetarium
programs,
fetched the link and entered in the download links in XEphem,
deleted
all catalogs and reloaded them several times. I get for unusual,
magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
deleted the .edb and generated them again. See object 2010
JT123, what
magnitude do you have for this object? I compiled the lastest
version
and i'm running it on Debian, XEphem 3.7.6
Best Regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@... <mailto:santiago@...>
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
El 21/11/14 a las 15:04, ecdowney@...
<mailto:ecdowney@...> [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
>
>
> You do realize that Downloading just stores them on disk,
right? You
> must still Load them using Data -> Files.
>
>
>
>
--
-- Wayne
--
-- Wayne
|
is one place; I checked for your asteroids they are there, maybe with a different primary name? --W
On Tue, Dec 9, 2014 at 9:17 AM, Wayne Green <dxwayne@...> wrote: Hey,
using xephem 3.7.7-RC3
I checked JPL and the MPC for the object 2010 JT123, for which they show an updated name of 2014 FD7. I don't find either name in the .edb files from Lowell or
the MPC bright, or dim, even after update.
MPC directly reports the mag as 23.2ish for now.
JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
Can you send me the filename and line from your .edb file?
grep? '2014.*FD7' ?? *edb
and
grep? '2010.*JT123'?? *edb
I don't get any output for either query. check your install
base (mine is /usr/local/xephem/catalogs) and from
your ~/.xephem dir.
During this chase, I deleted? files from /usr/share/xephem/catalogs...
Reran the app.
Found MPC files in my ~/.xephem directory!
deleted those
reloaded
So, I asked the MPC for the single line for XEphem, and saved this
into a file in ~/.xephem/ast.edb and I can find, load, query, and
Sky Point the 2014*FD7 critter.
The mag reports fine.
# From MPO315289 (HACKED HERE, OK in ast.edb attached)
2014 FD7,e,15.4565,187.2564,138.8035
,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
Attached is the hacked output from a JPL vector query
with object data from JPL and the hacked table
from the MPC direct query.
I realize you are not looking for these data exactly, but
trying to solve the XEphem .edb issue, but here is
the 'truth' from my two main sources for a baseline
for debugging.
I don't have a lot of time to dig into the code, but hope this
helps. Good first cup of coffee exercise for me this AM!
--Wayne
|
So, where i can download correctly the orbital elements file from the
MPC? Do they support XEphem as they claim in their page?
Best regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
toggle quoted message
Show quoted text
El 10/12/14 a las 13:50, Wayne Green dxwayne@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
et Viola!
The line you have in Soft03Unusual.edb has a field:
'H,'
that should read:
'H21.5,'
That carries the asteroid 'H=absolute magnitude' upon which
the angles and distances are used to compute the observable
magnitude at that time.
Your Soft03Unusual.edb is in error.
If you hack the little 21.5 into the field you should be
good.
I tested all this by adding the line to the little ast.edb file
from yesterday.
2010 JT123,e,19.4655,181.8817, 17.8247,1.538878,\
0.5162950,0.12347507, 353.8033, 05/04.0/2010,2000, H, 0.15
(for those following along: backslash is mine to fold line
for email 8,\<cr>0.51... should be run together 8,051...)
The line as above rendered a 3.9 mag.
The mag worked fine for me after
changing the H, to H21.5,
rendering 25.4
--Wayne
On Tue, Dec 9, 2014 at 9:28 PM, Santiago Roland santiago@...
<mailto:santiago@...> [xephem] <xephem@...
<mailto:xephem@...>> wrote:
__
Well, i still have this issue. I deleted all asteroid catalogs in
/usr/local/xephem/catalogs and /home/user/.xephem with no luck, the
Unusual asteroids still show in wrong magnitudes. Both grep commands
are this:
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep JT123
2010
JT123,e,19.4655,181.8817,17.8247,1.538878,0.5162950,0.12347507,353.8033,05/04.0/2010,2000,H,0.15
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep FD7
2010
FD7,e,6.1775,357.5167,269.2413,2.584144,0.2372624,0.68540045,344.9729,05/23.0/2014,2000,H22.1,0.15
2014
FD7,e,15.4618,187.2578,138.7606,1.203125,0.7468576,0.04899253,261.4664,05/23.0/2014,2000,H21.5,0.15
observador@orion:~/.xephem$
Best regards,
--
Santiago Roland.-
---------------------------------
Jabber: santiago.roland@... <mailto:santiago.roland@...>
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
On Tue, Dec 09, 2014 at 09:17:28AM -0700, Wayne Green
dxwayne@... <mailto:dxwayne@...> [xephem] wrote:
>
> [[1]Attachment(s) from Wayne Green included below]
>
> Hey,
>
> using xephem 3.7.7-RC3
> I checked JPL and the MPC for the object 2010 JT123, for which
> they show an updated name of 2014 FD7.
>
> I don't find either name in the .edb files from Lowell or
> the MPC bright, or dim, even after update.
>
> MPC directly reports the mag as 23.2ish for now.
>
> JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
>
> Can you send me the filename and line from your .edb file?
>
> grep '2014.*FD7' *edb
> and
> grep '2010.*JT123' *edb
>
> I don't get any output for either query. check your install
> base (mine is /usr/local/xephem/catalogs) and from
> your ~/.xephem dir.
>
> During this chase, I deleted files from /usr/share/xephem/catalogs...
> Reran the app.
> Found MPC files in my ~/.xephem directory!
> deleted those
> reloaded
>
> So, I asked the MPC for the single line for XEphem, and saved this
> into a file in ~/.xephem/ast.edb and I can find, load, query, and
> Sky Point the 2014*FD7 critter.
>
> The mag reports fine.
>
> # From MPO315289 (HACKED HERE, OK in ast.edb attached)
> 2014 FD7,e,15.4565,187.2564,138.8035
> ,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
>
> Attached is the hacked output from a JPL vector query
> with object data from JPL and the hacked table
> from the MPC direct query.
>
> I realize you are not looking for these data exactly, but
> trying to solve the XEphem .edb issue, but here is
> the 'truth' from my two main sources for a baseline
> for debugging.
>
> I don't have a lot of time to dig into the code, but hope this
> helps. Good first cup of coffee exercise for me this AM!
>
> --Wayne
>
> On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland
[2]santiago@... <mailto:santiago@...>
> [xephem] <[3]xephem@...
<mailto:xephem@...>> wrote:
>
>
>
> Yeah, i keep having the same problem. I downloaded the Lowell dim
> catalog and magnitudes are fine, The issue is with the MPC files. I
> downloaded them in the orbital elements page for planetarium programs,
> fetched the link and entered in the download links in XEphem, deleted
> all catalogs and reloaded them several times. I get for unusual,
> magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
> deleted the .edb and generated them again. See object 2010 JT123, what
> magnitude do you have for this object? I compiled the lastest version
> and i'm running it on Debian, XEphem 3.7.6
>
> Best Regards,
>
> Santiago Roland.-
> ---------------------------------
> Jabber: [4]santiago@...
<mailto:santiago@...>
> Diaspora*: [5]
> Identi.ca: [6]
> openPGP ID: 7BE512C5
> openPGP key: [7]
> ---------------------------------
>
> El 21/11/14 a las 15:04, [8]ecdowney@...
<mailto:ecdowney@...> [xephem]
> ±ð²õ³¦°ù¾±²ú¾±¨®:
> >
> >
> > You do realize that Downloading just stores them on disk, right? You
> > must still Load them using Data -> Files.
> >
> >
> >
> >
>
> --
> -- Wayne
>
>
>
>References
>
> Visible links
> 1. file:///tmp/mutt.html#TopText
> 2. mailto:santiago@... <mailto:santiago@...>
> 3. mailto:xephem@... <mailto:xephem@...>
> 4. mailto:santiago@... <mailto:santiago@...>
> 5.
> 6.
> 7.
> 8. mailto:ecdowney@...
<mailto:ecdowney@...>
> 9.
;_ylc=X3oDMTJxaWZxcHByBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNhdHRhY2htZW50BHNsawN2aWV3T25XZWIEc3RpbWUDMTQxODE0MTg1MA--
> 10. Xep1.txt
>
> 11. ast.edb
>
> 12.
;_ylc=X3oDMTJwZTgxY3A0BF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BG1zZ0lkAzM0NTQEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxNDE4MTQxODUw?act=reply&messageNum=3454
> 13. mailto:dxwayne@...
<mailto:dxwayne@...>?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
> 14. mailto:xephem@...
<mailto:xephem@...>?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
> 15.
;_ylc=X3oDMTJlc2Y2ZnVmBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNmdHIEc2xrA250cGMEc3RpbWUDMTQxODE0MTg1MA--
> 16.
;_ylc=X3oDMTM0OHRhMmo5BF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BG1zZ0lkAzM0NTQEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxNDE4MTQxODUwBHRwY0lkAzM0MzY-
> 17.
;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
> 18.
;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
> 19.
;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
> 20.
;_ylc=X3oDMTJlMXU2aDEzBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTQxODE0MTg1MA--
> 21.
;_ylc=X3oDMTJkZmsyMHI3BF9TAzk3NDc2NTkwBGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNDE4MTQxODUw
> 22.
> 23. mailto:xephem-unsubscribe@...
<mailto:xephem-unsubscribe@...>?subject=Unsubscribe
> 24.
>p11-kit: invalid config filename, will be ignored in the future:
/etc/pkcs11/modules/gnome-keyring-module
--
-- Wayne
|
et Viola!
The line you have in Soft03Unusual.edb has a field: 'H,' that should read: 'H21.5,' That carries the asteroid 'H=absolute magnitude' upon which the angles and distances are used to compute the observable magnitude at that time. Your Soft03Unusual.edb is in error. If you hack the little 21.5 into the field you should be good. I tested all this by adding the line to the little ast.edb file from yesterday. 2010 JT123,e,19.4655,181.8817, 17.8247,1.538878,\ 0.5162950,0.12347507, 353.8033, 05/04.0/2010,2000, H,??? 0.15 (for those following along: backslash is mine to fold line
for email ?? 8,\0.51... should be run together 8,051...)
The line as above rendered a 3.9? mag.
The mag worked fine for me after
changing the H, to H21.5,
rendering 25.4
--Wayne
On Tue, Dec 9, 2014 at 9:28 PM, Santiago Roland santiago@... [xephem] <xephem@...> wrote:
?
Well, i still have this issue. I deleted all asteroid catalogs in /usr/local/xephem/catalogs and /home/user/.xephem with no luck, the Unusual asteroids still show in wrong magnitudes. Both grep commands are this:
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep JT123
2010 JT123,e,19.4655,181.8817,17.8247,1.538878,0.5162950,0.12347507,353.8033,05/04.0/2010,2000,H,0.15
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep FD7
2010 FD7,e,6.1775,357.5167,269.2413,2.584144,0.2372624,0.68540045,344.9729,05/23.0/2014,2000,H22.1,0.15
2014 FD7,e,15.4618,187.2578,138.7606,1.203125,0.7468576,0.04899253,261.4664,05/23.0/2014,2000,H21.5,0.15
observador@orion:~/.xephem$
Best regards,
--
Santiago Roland.-
---------------------------------
Jabber: santiago.roland@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
On Tue, Dec 09, 2014 at 09:17:28AM -0700, Wayne Green dxwayne@... [xephem] wrote:
> ?
> [[1]Attachment(s) from Wayne Green included below]
>
> Hey,
>
> using xephem 3.7.7-RC3
> I checked JPL and the MPC for the object 2010 JT123, for which
> they show an updated name of 2014 FD7.
>
> I don't find either name in the .edb files from Lowell or
> the MPC bright, or dim, even after update.
>
> MPC directly reports the mag as 23.2ish for now.
>
> JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
>
> Can you send me the filename and line from your .edb file?
>
> grep? '2014.*FD7' ?? *edb
> and
> grep? '2010.*JT123'?? *edb
>
> I don't get any output for either query. check your install
> base (mine is /usr/local/xephem/catalogs) and from
> your ~/.xephem dir.
>
> During this chase, I deleted? files from /usr/share/xephem/catalogs...
> Reran the app.
> Found MPC files in my ~/.xephem directory!
> deleted those
> reloaded
>
> So, I asked the MPC for the single line for XEphem, and saved this
> into a file in ~/.xephem/ast.edb and I can find, load, query, and
> Sky Point the 2014*FD7 critter.
>
> The mag reports fine.
>
> # From MPO315289 (HACKED HERE, OK in ast.edb attached)
> 2014 FD7,e,15.4565,187.2564,138.8035
> ,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
>
> Attached is the hacked output from a JPL vector query
> with object data from JPL and the hacked table
> from the MPC direct query.
>
> I realize you are not looking for these data exactly, but
> trying to solve the XEphem .edb issue, but here is
> the 'truth' from my two main sources for a baseline
> for debugging.
>
> I don't have a lot of time to dig into the code, but hope this
> helps. Good first cup of coffee exercise for me this AM!
>
> --Wayne
>
> On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland [2]santiago@...
> [xephem] <[3]xephem@...> wrote:
>
> ?
>
> Yeah, i keep having the same problem. I downloaded the Lowell dim
> catalog and magnitudes are fine, The issue is with the MPC files. I
> downloaded them in the orbital elements page for planetarium programs,
> fetched the link and entered in the download links in XEphem, deleted
> all catalogs and reloaded them several times. I get for unusual,
> magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
> deleted the .edb and generated them again. See object 2010 JT123, what
> magnitude do you have for this object? I compiled the lastest version
> and i'm running it on Debian, XEphem 3.7.6
>
> Best Regards,
>
> Santiago Roland.-
> ---------------------------------
> Jabber: [4]santiago@...
> Diaspora*: [5]
> Identi.ca: [6]
> openPGP ID: 7BE512C5
> openPGP key: [7]
> ---------------------------------
>
> El 21/11/14 a las 15:04, [8]ecdowney@... [xephem]
> ±ð²õ³¦°ù¾±²ú¾±¨®:
> >
> >
> > You do realize that Downloading just stores them on disk, right? You
> > must still Load them using Data -> Files.
> >
> >
> >
> >
>
> --
> -- Wayne
>
>
>
>References
>
> Visible links
> 1. file:///tmp/mutt.html#TopText
> 2. mailto:santiago@...
> 3. mailto:xephem@...
> 4. mailto:santiago@...
> 5.
> 6.
> 7.
> 8. mailto:ecdowney@...
> 9.
> 10. Xep1.txt
>
> 11. ast.edb
>
> 12.
> 13. mailto:dxwayne@...?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
> 14. mailto:xephem@...?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
> 15.
> 16.
> 17.
> 18.
> 19.
> 20.
> 21.
> 22.
> 23. mailto:xephem-unsubscribe@...?subject=Unsubscribe
> 24.
>p11-kit: invalid config filename, will be ignored in the future: /etc/pkcs11/modules/gnome-keyring-module
|
Re: Magnitude problem [2 Attachments]
Well, i still have this issue. I deleted all asteroid catalogs in /usr/local/xephem/catalogs and /home/user/.xephem with no luck, the Unusual asteroids still show in wrong magnitudes. Both grep commands are this:
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep JT123
2010 JT123,e,19.4655,181.8817,17.8247,1.538878,0.5162950,0.12347507,353.8033,05/04.0/2010,2000,H,0.15
observador@orion:~/.xephem$ cat Soft03Unusual.edb | grep FD7
2010 FD7,e,6.1775,357.5167,269.2413,2.584144,0.2372624,0.68540045,344.9729,05/23.0/2014,2000,H22.1,0.15
2014 FD7,e,15.4618,187.2578,138.7606,1.203125,0.7468576,0.04899253,261.4664,05/23.0/2014,2000,H21.5,0.15
observador@orion:~/.xephem$
Best regards,
--
Santiago Roland.-
---------------------------------
Jabber: santiago.roland@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
toggle quoted message
Show quoted text
On Tue, Dec 09, 2014 at 09:17:28AM -0700, Wayne Green dxwayne@... [xephem] wrote: ?
[[1]Attachment(s) from Wayne Green included below]
Hey,
using xephem 3.7.7-RC3
I checked JPL and the MPC for the object 2010 JT123, for which
they show an updated name of 2014 FD7.
I don't find either name in the .edb files from Lowell or
the MPC bright, or dim, even after update.
MPC directly reports the mag as 23.2ish for now.
JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
Can you send me the filename and line from your .edb file?
grep? '2014.*FD7' ?? *edb
and
grep? '2010.*JT123'?? *edb
I don't get any output for either query. check your install
base (mine is /usr/local/xephem/catalogs) and from
your ~/.xephem dir.
During this chase, I deleted? files from /usr/share/xephem/catalogs...
Reran the app.
Found MPC files in my ~/.xephem directory!
deleted those
reloaded
So, I asked the MPC for the single line for XEphem, and saved this
into a file in ~/.xephem/ast.edb and I can find, load, query, and
Sky Point the 2014*FD7 critter.
The mag reports fine.
# From MPO315289 (HACKED HERE, OK in ast.edb attached)
2014 FD7,e,15.4565,187.2564,138.8035
,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
Attached is the hacked output from a JPL vector query
with object data from JPL and the hacked table
from the MPC direct query.
I realize you are not looking for these data exactly, but
trying to solve the XEphem .edb issue, but here is
the 'truth' from my two main sources for a baseline
for debugging.
I don't have a lot of time to dig into the code, but hope this
helps. Good first cup of coffee exercise for me this AM!
--Wayne
On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland [2]santiago@...
[xephem] <[3]xephem@...> wrote:
?
Yeah, i keep having the same problem. I downloaded the Lowell dim
catalog and magnitudes are fine, The issue is with the MPC files. I
downloaded them in the orbital elements page for planetarium programs,
fetched the link and entered in the download links in XEphem, deleted
all catalogs and reloaded them several times. I get for unusual,
magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
deleted the .edb and generated them again. See object 2010 JT123, what
magnitude do you have for this object? I compiled the lastest version
and i'm running it on Debian, XEphem 3.7.6
Best Regards,
Santiago Roland.-
---------------------------------
Jabber: [4]santiago@...
Diaspora*: [5]
Identi.ca: [6]
openPGP ID: 7BE512C5
openPGP key: [7]
---------------------------------
El 21/11/14 a las 15:04, [8]ecdowney@... [xephem]
±ð²õ³¦°ù¾±²ú¾±¨®:
>
>
> You do realize that Downloading just stores them on disk, right? You
> must still Load them using Data -> Files.
>
>
>
>
--
-- Wayne
References
Visible links
1. file:///tmp/mutt.html#TopText
2. mailto:santiago@...
3. mailto:xephem@...
4. mailto:santiago@...
5.
6.
7.
8. mailto:ecdowney@...
9. ;_ylc=X3oDMTJxaWZxcHByBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNhdHRhY2htZW50BHNsawN2aWV3T25XZWIEc3RpbWUDMTQxODE0MTg1MA--
10. Xep1.txt
11. ast.edb
12. ;_ylc=X3oDMTJwZTgxY3A0BF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BG1zZ0lkAzM0NTQEc2VjA2Z0cgRzbGsDcnBseQRzdGltZQMxNDE4MTQxODUw?act=reply&messageNum=3454
13. mailto:dxwayne@...?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
14. mailto:xephem@...?subject=Re%3A%20%5Bxephem%5D%20Re%3A%20Magnitude%20problem
15. ;_ylc=X3oDMTJlc2Y2ZnVmBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNmdHIEc2xrA250cGMEc3RpbWUDMTQxODE0MTg1MA--
16. ;_ylc=X3oDMTM0OHRhMmo5BF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BG1zZ0lkAzM0NTQEc2VjA2Z0cgRzbGsDdnRwYwRzdGltZQMxNDE4MTQxODUwBHRwY0lkAzM0MzY-
17. ;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
18. ;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
19. ;_ylc=X3oDMTE4M3R1OW82BF9TAzk3MzU5NzE0BGNmOQNQSE9UT01BVElDBHNlYwNtZWdhcGhvbmU-
20. ;_ylc=X3oDMTJlMXU2aDEzBF9TAzk3MzU5NzE0BGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTQxODE0MTg1MA--
21. ;_ylc=X3oDMTJkZmsyMHI3BF9TAzk3NDc2NTkwBGdycElkAzI3MDQ3NTAEZ3Jwc3BJZAMxNzA1MDgyODA1BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxNDE4MTQxODUw
22.
23. mailto:xephem-unsubscribe@...?subject=Unsubscribe
24.
p11-kit: invalid config filename, will be ignored in the future: /etc/pkcs11/modules/gnome-keyring-module
|
Re: Magnitude problem [2 Attachments]
|
Hey,
using xephem 3.7.7-RC3
I checked JPL and the MPC for the object 2010 JT123, for which they show an updated name of 2014 FD7. I don't find either name in the .edb files from Lowell or
the MPC bright, or dim, even after update.
MPC directly reports the mag as 23.2ish for now.
JPL sez the object has a heliocentric distance ~1.52e8km (1AU).
Can you send me the filename and line from your .edb file?
grep? '2014.*FD7' ?? *edb
and
grep? '2010.*JT123'?? *edb
I don't get any output for either query. check your install
base (mine is /usr/local/xephem/catalogs) and from
your ~/.xephem dir.
During this chase, I deleted? files from /usr/share/xephem/catalogs...
Reran the app.
Found MPC files in my ~/.xephem directory!
deleted those
reloaded
So, I asked the MPC for the single line for XEphem, and saved this
into a file in ~/.xephem/ast.edb and I can find, load, query, and
Sky Point the 2014*FD7 critter.
The mag reports fine.
# From MPO315289 (HACKED HERE, OK in ast.edb attached)
2014 FD7,e,15.4565,187.2564,138.8035
,1.203030,0.7469466,0.048986,50.8130,12/09.0/2014,2000,H21.5,0.15
Attached is the hacked output from a JPL vector query
with object data from JPL and the hacked table
from the MPC direct query.
I realize you are not looking for these data exactly, but
trying to solve the XEphem .edb issue, but here is
the 'truth' from my two main sources for a baseline
for debugging.
I don't have a lot of time to dig into the code, but hope this
helps. Good first cup of coffee exercise for me this AM!
--Wayne
On Tue, Dec 9, 2014 at 5:37 AM, Santiago Roland santiago@... [xephem] <xephem@...> wrote:
?
Yeah, i keep having the same problem. I downloaded the Lowell dim
catalog and magnitudes are fine, The issue is with the MPC files. I
downloaded them in the orbital elements page for planetarium programs,
fetched the link and entered in the download links in XEphem, deleted
all catalogs and reloaded them several times. I get for unusual,
magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
deleted the .edb and generated them again. See object 2010 JT123, what
magnitude do you have for this object? I compiled the lastest version
and i'm running it on Debian, XEphem 3.7.6
Best Regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
El 21/11/14 a las 15:04, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
>
>
> You do realize that Downloading just stores them on disk, right? You
> must still Load them using Data -> Files.
>
>
>
>
|
And also detected other problem that is maybe related to the magnitude
problem. It is in the numbering of the asteroids, see in the screen i
toggled high magnitude for a panorama view of bright asteroids and
notices the asteroid 1 Irene and 2 Amphitrite, they are 14 and 29
numbered, so maybe this issue is related with the magnitude one. Is
somebody having this problem? or just me? I compiled the latest version,
and i'm running Debian Wheezy 7.0 with backports repository.
See the screenshot.
Best regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
toggle quoted message
Show quoted text
El 21/11/14 a las 15:04, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
You do realize that Downloading just stores them on disk, right? You
must still Load them using Data -> Files.
|
Yeah, i keep having the same problem. I downloaded the Lowell dim
catalog and magnitudes are fine, The issue is with the MPC files. I
downloaded them in the orbital elements page for planetarium programs,
fetched the link and entered in the download links in XEphem, deleted
all catalogs and reloaded them several times. I get for unusual,
magnitudes around 3 or 4. Any other ideas? Logs that i can post? I
deleted the .edb and generated them again. See object 2010 JT123, what
magnitude do you have for this object? I compiled the lastest version
and i'm running it on Debian, XEphem 3.7.6
Best Regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
toggle quoted message
Show quoted text
El 21/11/14 a las 15:04, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
You do realize that Downloading just stores them on disk, right? You
must still Load them using Data -> Files.
|
Re: Creating object lists?
Manual included in download bundle has full details on format of object list input format, for either fixed objects (stars, galaxies, etc.) or orbital elements.? The data fields (name, R.A., Dec., type, etc.) are separated by commas (.csv),? so don't use a comma in the name field!?
I generate custom lists from various catalog search sites like CDS Vizier, download them from the site and open with Excel.? Excel has a Save As ...? .csv option.? If you used/created more than one worksheet in the Excel file, Excel will ask if o.k. to save active worksheet only.? After doing that re-save your multi-sheet set as Excel workbook (.xlsb).?
You may still have to edit the .csv file a bit.? For XEphem on MacOS I use an awk script to replace the line terminators with Unix type.? As I recall this and some other format discrepancies may cause XEphem to crash (vanish) when you try to read in your new object file.
All that remains after formatting is putting it where XEphem looks for catalogs.? As described in the Install readme, that depends on how you installed and set up XEphem's environment.?
I've suggested to Elwood in the past to add an object type to represent a user's object list.
In the meantime I pirate some existing XEphem faint irrelevant object type & symbol like SNRs (R) or galaxy clusters (A).?? Also I make liberal use of the synonyms option in the name field, putting in other data like IR flux,? observing proposal ID no.,? estimated integration time, etc. etc. all separated by | .? Then one can just right mouse click on the sky view symbol to see all that displayed for that object.?
Make sure you load your custom list before loading any XEphem supplied catalog that may contain any of the same objects.? The sensible default is to not display a second entry for the same object.? See Preferences for adjusting criteria for that or disabling it.?
Small subsets of your big custom object list(s) can be created and saved as favorites lists, named in a helpful way, e.g. "W-R_summer_V<10.fav".?
|
Re: 11/25/2014 4:52:01 AM
On 2014-11-24 23:52, 'peregil2007' peregil2007@... [xephem] wrote: ?
This member has been placed on moderated status. -- John Perry - WX5JP
|
|
|
Current purchased versions of XEphem have UCAC4 in the download tars. ? But see Teixeira article re bad UCAC proper motions for V>12
from Allan Meyer's cell phone
toggle quoted message
Show quoted text
On Nov 20, 2014, at 12:52 AM, xephem@... wrote:
Messages
Wed Nov?19,?2014 1:43?pm (PST) . Posted by:
Where i can download xephem friendly star catalogues for astrometry? I
would like to download USNO B1, UCAC 4, maybe NOMAD catalog... are those
compatible with xephem? I've been using USNO A2.0 for many years but i
need to upgrade...
Thanks,
--
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
:
openPGP ID: 7BE512C5
openPGP key:
------------ --------- --------- ---
Wed Nov?19,?2014 7:51?pm (PST) . Posted by:
On 11/19/2014 04:42 PM, Santiago Roland santiago@... [xephem] wrote:
> Where i can download xephem friendly star catalogues for astrometry? I
> would like to download USNO B1, UCAC 4, maybe NOMAD catalog... are those
> compatible with xephem? I've been using USNO A2.0 for many years but i
> need to upgrade...
Neither USNO B1 nor NOMAD are available for download, they
are too large.
To get a copy of UCAC4 send email to
brenda.hicks@... with a subject
line of UCAC4.
Wed Nov?19,?2014 1:46?pm (PST) . Posted by:
I downloaded the latest files from MPC (the links are shown in the
screenshot), maybe they were not updates properly? I also hit the
download button for Lowell and AstMPC_dim... will try again...
Best regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
El 12/11/14 a las 02:40, ecdowney@... [xephem] ±ð²õ³¦°ù¾±²ú¾±¨®:
>
>
> Like it says, your ephemerides are out of date, which means the
> location, and hence magnitudes, for your object are unreliable.
>
>
> I just downloaded the latest elements from Lowell and 2010 OU100 is
> reported as being magnitude 21.7.
>
>
|
I purchased my USNO A2.0 on Ebay (of all places) years ago.
-Karl
|
You do realize that Downloading just stores them on disk, right? You must still Load them using Data -> Files.
|
Yes, i know that USNO B1 it's like 80GB or so, but for todays storage
capacity would not be that much problem, just a 1-week torrent download
or 2. Maybe it was available in some FTP server or torrent. I found a
russian torrent page, but it was broken. We have to do field
recognitions in mag 18 and 19 so we need a dimmer catalog than UCAC. In
the moment we use USNO A2.0 which is dim enough, but it does not have
all stars and sometimes it's confusing... we also use Aladin Sky Altas,
the web java applet that loads all catalogs. I was hoping to use xephem
with a local repository of USNO B1, the same way we use USNO A2.0.
Best regards,
Santiago Roland.-
---------------------------------
Jabber: santiago@...
Diaspora*:
Identi.ca:
openPGP ID: 7BE512C5
openPGP key:
---------------------------------
El 20/11/14 a las 01:51, Greg Hennessy greg.hennessy@... [xephem]
±ð²õ³¦°ù¾±²ú¾±¨®:
toggle quoted message
Show quoted text
On 11/19/2014 04:42 PM, Santiago Roland santiago@... [xephem] wrote:
Where i can download xephem friendly star catalogues for astrometry? I
would like to download USNO B1, UCAC 4, maybe NOMAD catalog... are those
compatible with xephem? I've been using USNO A2.0 for many years but i
need to upgrade... Neither USNO B1 nor NOMAD are available for download, they
are too large.
To get a copy of UCAC4 send email to
brenda.hicks@... with a subject
line of UCAC4.
|
