-
Notifications
You must be signed in to change notification settings - Fork 3
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
add more sites #15
add more sites #15
Conversation
@cole-brokamp can you check that the new isochrone files are at |
I'm trying to wean myself off of Transmit too. Here's an
It returned nothing for me, so I did this one to double check:
That did return what I expected, so I think that it is not available. |
Doing more digging and it is available, but not in the
|
Everything in |
I tried to move the whole isochrones folder but I think I misunderstood the usage of |
Then you can run without the |
I think I want to keep the ones in the isochrones folder and delete the ones from the drivetime folder. i.e., delete: |
also, is there a way to check the permissions using the cli? |
note: cleveland clinic address provided by pac3 here was already included |
Not without going a little deeper with the aws cli tool. I made those changes in the AWS S3 console -- you don't have access to that right now, but I think we can change that if you want to use it in the future. |
I think the error messages are a little deceiving here because all of the Dockerfile steps are run in parallel. If one of them errors, then all other ones are canceled, and all of those 403 errors appear. This usually isn't a problem, but might be an issue with this many large number of Dockerfile instructions steps. I figured out the offending line by commenting out all but one of the |
Oh, good catch. I didn't think about the |
I would avoid manually editing |
We need drivetime codes created for these 5 PAC3 centers. If time or resources is a concern, could we please prioritize creating a drivetime code for Vanderbilt? Their files are prepped and ready to run. |
Thanks for the update, we will get to adding these soon! |
continued in #16 |
No description provided.