Search found 14 matches

by MaximVoronkov
Sat Aug 28, 2010 1:51 am
Forum: MIRIAD
Topic: problem with UVSPLIT(?)
Replies: 5
Views: 24293

Re: problem with UVSPLIT(?)

I actually prefer to use uvaver instead of uvsplit in most my scripts (of course, without averaging in time or frequency). It gives a bit better control on what you want to split out.
by MaximVoronkov
Sat Aug 28, 2010 1:45 am
Forum: MIRIAD
Topic: IMFIT - gaussian fitting
Replies: 4
Views: 22864

Re: IMFIT - gaussian fitting

Technically, the uncertainty of the integral can be estimated from uncertainties of the peak and FWHM for a Gaussian. However, just thinking now about this I must say that I am not entirely sure what integral MIRIAD reports. Is it an integral over component (or components) or measured integral over ...
by MaximVoronkov
Sat Aug 07, 2010 10:25 am
Forum: Online Programs
Topic: CABBScheduler
Replies: 9
Views: 38647

Re: CABBScheduler

Hi Mark, First, thanks again for the Master/Slave feature. Without it, we probably wouldn't be able to do our yesterday's C1820 run successfully given the amount of other issues. I think something funny is still going on with the zoom config page. One thing which seems certain (because I've seen it ...
by MaximVoronkov
Wed Aug 04, 2010 1:05 pm
Forum: Online Programs
Topic: CABBScheduler
Replies: 9
Views: 38647

Re: CABBScheduler

Hi Mark, Just to follow the discussion over the morning tea about zoom setups. I thought a bit more about this and have the following suggestions which should be relatively straightforward to implement. 1. Allow the user to specify the velocity in the catalogue file (i.e. if there are extra columns ...
by MaximVoronkov
Fri Jun 18, 2010 4:10 pm
Forum: Online Programs
Topic: CABBScheduler
Replies: 9
Views: 38647

Re: CABBScheduler

Great! Thanks Mark.
by MaximVoronkov
Sat Jun 05, 2010 4:35 pm
Forum: MIRIAD
Topic: CABB data handling - fine tunining (buffers, ouput, etc)
Replies: 9
Views: 29856

Re: CABB data handling - fine tunining (buffers, ouput, etc)

And also forgot to mention that IFs are present in logical, but somewhat unexpected order: first IF broad, first zoom, second zoom ... 4th zoom, second IF broad, 5th zoom, ... 8th zoom.

Not an issue, just a comment.
by MaximVoronkov
Sat Jun 05, 2010 4:19 pm
Forum: MIRIAD
Topic: CABB data handling - fine tunining (buffers, ouput, etc)
Replies: 9
Views: 29856

Re: CABB data handling - fine tunining (buffers, ouput, etc)

Hi Mark, as Jamie said, I think the best route is to not use noif in atlod, you can then use window selection in subsequent task, which is much easier than trying to do it with explicit frequency selection. The selection mechanisms in miriad are already quite complex - the advice has always been to ...
by MaximVoronkov
Sat Jun 05, 2010 11:32 am
Forum: MIRIAD
Topic: CABB data handling - fine tunining (buffers, ouput, etc)
Replies: 9
Views: 29856

Re: CABB data handling - fine tunining (buffers, ouput, etc)

With noif option in atlod every zoom is mapped to a separate frequency configuration, so channel numbers become as expected. However, then most tasks don't distinguish between different zooms unless frequency(a,b) is specified explicitly in select keyword. It may be hard for closely located zooms. I...
by MaximVoronkov
Sat Jun 05, 2010 10:24 am
Forum: MIRIAD
Topic: CABB data handling - fine tunining (buffers, ouput, etc)
Replies: 9
Views: 29856

Re: CABB data handling - fine tunining (buffers, ouput, etc)

It looks like uvspec labels channels continuously for all spectral windows (i.e. both wide band and zoomed spectra). So, for the first zoom the channel numbers start from 2049, etc.
This was a bit unexpected, but I guess it is because I didn't use noif option in atlod
by MaximVoronkov
Sat Jun 05, 2010 8:37 am
Forum: MIRIAD
Topic: CABB data handling - fine tunining (buffers, ouput, etc)
Replies: 9
Views: 29856

Re: CABB data handling - fine tunining (buffers, ouput, etc)

I've just looked at some zoom mode data and found that uvindex reports zero increment for zoom bands (because the
increment is too small with 1 MHz zoom). It would be good to show more digits after decimal point or even use an
exponential notation.