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

WSclean Stimela error: error writing to FITS file #726

Open
Kincaidr opened this issue Jul 4, 2021 · 8 comments
Open

WSclean Stimela error: error writing to FITS file #726

Kincaidr opened this issue Jul 4, 2021 · 8 comments
Assignees

Comments

@Kincaidr
Copy link

Kincaidr commented Jul 4, 2021

I am trying to run wsclean for sources list file in a stimela script as:

image

I get the following error:

image

Full log file here:
log-wsclean_subtract_pt-point_source_selection.txt

@o-smirnov
Copy link
Collaborator

Disk space or disk quota problem?

@bennahugo
Copy link
Collaborator

Most likely disk space making the memmap fail.

@Kincaidr
Copy link
Author

Kincaidr commented Jul 5, 2021

These are my quotas:

image

I am running in a folder on vault-ike through ike: "kincaid@ike:~$ /net/ike/vault-ike/kincaid/" . . ., when running processes like this, does it check for space on the ike or vault-ike? Because ike is abit low on space.

@o-smirnov
Copy link
Collaborator

Disk quotas are per filesystem, and you can see that /home and /vault-ike are separate filesystems.

when running processes like this, does it check

It checks the quota at whichever location the process tries to write its data. The latter is up to the process. In the case of wsclean, it will write FITS files to the current directory obviously (unless -name includes a directory explicitly). It will also write temporary visibility data to the directory of the MS, unless you specify a -tmp-dir explicitly.

Anyway I bumped up your /vault-ike quota, try again?

@Kincaidr
Copy link
Author

Kincaidr commented Jul 5, 2021

Anyway I bumped up your /vault-ike quota, try again?

I have tried again, but I am still getting similar issue

@o-smirnov
Copy link
Collaborator

Can you try running the same wsclean command "by hand" outside the container? See if that goes through.

@Kincaidr
Copy link
Author

Kincaidr commented Jul 6, 2021

It runs successfully when i do it by hand

@o-smirnov
Copy link
Collaborator

OK that's odd. Seems to be a containerization issue then. @SpheMakh needs to look at this.

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

4 participants