Menu

#37 DSPSR usage

open
nobody
None
5
2011-01-10
2011-01-10
Natalia
No

Hi Willem,

ok I played around with NUTMAX and set it to several values up until 20 000, but everytime I get the same error message again after the reinstallation:

Tempo::predict input: ' 55506.6 55507.6'
Tempo::tempo system (tempo -z -f pulsar.eph << EOD
55506.6 55507.6
EOD
)
Unrecognised label: TZSITE
TZ source list for site = g

PSR Nspan Ncoeffs Maxha Freq
----------------------------------------------
0534+2200 120 15 12 8350.00000

Current date is 9-JAN-11, or MJD 55570.562

Enter first and last MJD, or hit return to run for today:
6-NOV-10 through 7-NOV-10

WARNING: time.dat too long, not all read
UT1 table overflow
Tempo::predict loading polyco.dat
****** BEGINNING OF FILE ******
********* END OF FILE *********
polyco::polyco this=0x28097f0
polyco::load (/tmp/tempo/polyco.dat)
polyco::load FILE*
polyco::load string*
polyco::load (string*) return npollys=0
polyco::~polyco this=0x28097f0

Error::stack
dsp::LoadToFold1::prepare
polyco::load(FILE*)
Error::InvalidState
Error::message
no polynomials loaded

When I re-run the make script of Tempo, I get the following warnings:

gfortran -ffixed-line-length-none -g -O2 -c -o tempo.o tempo.f
tempo.f:393.20:

do afmjd=fmjd1,fmjd2,tsid
1
Warning: Deleted feature: Loop variable at (1) must be integer
tempo.f:393.21:

do afmjd=fmjd1,fmjd2,tsid
1
Warning: Deleted feature: Start expression in DO loop at (1) must be integer
tempo.f:393.27:

do afmjd=fmjd1,fmjd2,tsid
1
Warning: Deleted feature: End expression in DO loop at (1) must be integer
tempo.f:393.33:

do afmjd=fmjd1,fmjd2,tsid
1

Warning: Deleted feature: Step expression in DO loop at (1) must be integer
gfortran -ffixed-line-length-none -g -O2 -c -o timcalc.o timcalc.f

At this point I assume that the functionality of Tempo is maybe limited due to the fact that I use gfortran as compiler and not g77 (?).
The NPT variable was set to 100000 when I started using Tempo. When I change this to a higher value, I get more warnings as described above.
However, it seems to me that the problem lies probably not only in the single parameters of Tempo.

Cheers,
Natalia

Discussion


Log in to post a comment.