Closed monocongo closed 2 years ago
Welcome to Astropy 👋 and thank you for your first issue!
A project member will respond to you as soon as possible; in the meantime, please double-check the guidelines for submitting issues and make sure you've provided the requested details.
GitHub issues in the Astropy repository are used to track bug reports and feature requests; If your issue poses a question about how to use Astropy, please instead raise your question in the Astropy Discourse user forum and close this issue.
If you feel that this issue has not been responded to in a timely manner, please leave a comment mentioning our software support engineer @embray, or send a message directly to the development mailing list. If the issue is urgent or sensitive in nature (e.g., a security vulnerability) please send an e-mail directly to the private e-mail feedback@astropy.org.
I don't see why you cannot change it in your instance to point to a place you can write to. Other HPC clusters have successfully done it and perhaps you could adopt their strategy. Have you read through https://docs.astropy.org/en/stable/config/index.html yet? Thanks.
If you have no control over this instance, please contact the service provider. I am not sure what we can do here.
Hi humans :wave: - this issue was labeled as Close? approximately 12 hours ago. If you think this issue should not be closed, a maintainer should remove the Close? label - otherwise, I will close this issue in 7 days.
If you believe I commented on this issue incorrectly, please report this here
Yes agreed, it looks like this can be taken care of with some configuration for astropy on the EMR cluster. I don't use astropy directly so this is my first exposure, I didn't know there was this local .astropy directory being created, etc., I'm just using sbpy for converting asteroid designations, and I can do that outside of an EMR job so I've just done the work needing sbpy locally and it works fine. In any event I really appreciate the fast attention to this issue and for the guidance to the configuration options, @pllim. Thank you!
Yes, indeed astropy
creates a ~/.astropy
for caching and config storing by default. I hope you could find a config that works for you. Good luck!
Bmmk
On Sat, Jul 30, 2022, 3:42 PM P. L. Lim @.***> wrote:
Yes, indeed astropy creates a ~/.astropy for caching and config storing by default. I hope you could find a config that works for you. Good luck!
— Reply to this email directly, view it on GitHub https://github.com/astropy/astropy/issues/13512#issuecomment-1200298783, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKEIHQN737TT2KLTDMROKDVWWOUNANCNFSM547JR6JQ . You are receiving this because you modified the open/close state.Message ID: @.***>
Description
When I run a Jupyter notebook in AWS EMR using PySpark kernel I get a permission denied error when I run the first cell which contains an import of
sbpy
, it looks like astropy is trying to access '/home/.astropy', which probably just doesn't exist on the EC2 where the EMR notebook is running. How do we configure things so this won't happen and astropy can initialize without trying to access this location?Expected behavior
I expected for
sbpy
to be imported without an error.Actual behavior
Steps to Reproduce
sbpy.data.Names
System Details
Results of the above from EMR notebook cell: Linux-4.14.281-212.502.amzn2.x86_64-x86_64-with-glibc2.2.5 Python 3.7.10 (default, Jun 3 2021, 00:02:01) [GCC 7.3.1 20180712 (Red Hat 7.3.1-13)] Numpy 1.20.0 pyerfa 2.0.0.1 astropy 4.3.1 Scipy 1.7.3