Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for referenced Measurement Sets #1

Open
bmarcote opened this issue Dec 2, 2020 · 1 comment
Open

Support for referenced Measurement Sets #1

bmarcote opened this issue Dec 2, 2020 · 1 comment

Comments

@bmarcote
Copy link
Contributor

bmarcote commented Dec 2, 2020

The current scripts do not support MS files that contain referenced tables (e.g. when a MS which is a subset of a main one is created but instead of duplicating the tables that remain the same they are still referring to the original ones, avoiding duplicities).

It would require to change the calls to subtables, like:

tb.open(vis + '/ANTENNA')

to use the tb.getkeyword('ANTENNA') command to retrieve the actual location of the table. It would still recover the same behavior for the standard MS. No further changes should be required.

I am aware that in pyrap tables it can all be done directly with e.g. pt.table( pt.table(vis, ...).getkeyword('ANTENNA') ). However, from casac it seems like the tb.getkeyword() function adds (according to its documentation) the string 'Table: ' before the path to the table (e.g. -> 'Table: /data0/marcote/N20C3/n20c3.ms/ANTENNA'). Not sure if there is then an alternate way or it would only require to trim this part of the string.

@kettenis
Copy link
Member

kettenis commented Dec 7, 2020

Hi Benito,
You did something I didn't anticipate. I'll see if I can find a way to fix this.
Cheers,
Mark

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants