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

subdividing FL for wv2 processing project #3

Closed
7yl4r opened this issue Jun 4, 2018 · 16 comments
Closed

subdividing FL for wv2 processing project #3

7yl4r opened this issue Jun 4, 2018 · 16 comments
Labels

Comments

@7yl4r
Copy link
Member

7yl4r commented Jun 4, 2018

@mjm8 : I think we spoke briefly about dividing up the area we intend to cover under the microsoft grant. You may already have something better figured out, but I was thinking we could use the same subdivisions as FCMaP to divide up FL.

Based on those subdivisions I am thinking we run "big bend" and "West FL Pen." on our servers & do the others in microsoft's cloud.

@7yl4r 7yl4r added the question label Jun 4, 2018
@mjm8
Copy link
Collaborator

mjm8 commented Jun 11, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 11, 2018

It is relatively trivial for me to re-organize images once I have indexed them, so we can use whatever organization paradigm works best for you (and others(?) accessing wv2 data). We can even keep using /extra_data if desired.

That being said, I would most prefer to organize the images using this imars-objects spec - which is very near to what you propose. In this case I think it would look something like:

/big_bend
    /wv2
        /...
        /2017
        /2018
/fl_se
    /wv2
        /...
        /2017
        /2018
/fl_ne
    /wv2
        /...
        /2017
        /2018
/monroe
    /wv2
        /...
        /2017
        /2018
/panhandle
    /wv2
        /...
        /2017
        /2018
/west_fl_pen
    /wv2
        /...
        /2017
        /2018

it might also be nice to split up the different files by subdividing wv2 somehow. eg:

/big_bend
    /wv2_m1bs
    /wv2_p1bs

...but only if that subdivision won't cause any issues for your (or others) processing routines.

@mjm8
Copy link
Collaborator

mjm8 commented Jun 11, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 27, 2018

The initial tests have gone well enough. Still a few bugs to iron out, but nothing major.

I would like to start processing the big bend region on our servers here. I think the easiest way to do this will be to set up ftp downloads from digital globe as we were before, using the filename convention wv2_YYYY-MM-DDThhmm_big_bend.zip, where the datetime used is the time the order is placed.

What do you think @mjm8 ?

7yl4r added a commit to USF-IMARS/imars-etl that referenced this issue Jun 27, 2018
@mjm8
Copy link
Collaborator

mjm8 commented Jun 28, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 28, 2018

how many images (2? 10? 100?)

I think we need a few 100 to keep the servers busy while I explore optimizations.

start downloading them individually through the DG portal

Ouch. If this is the case I can get creative with automating it, but it would be much better for everyone if DG exposed an API. We'll talk more on that later I suppose.

the images we already have, which includes all of the Big Bend for 2014/2015 [ ... ] and where I should put that

Oh, perfect! Ultimately we need to "load" them using this imars-etl tool I have been working on. This puts the metadata into a database and copies the file to /srv/imars-objects/big_bend/wv2/ so all the servers can find them. Do you have a list of the files or are the all in a directory?

@mjm8
Copy link
Collaborator

mjm8 commented Jun 28, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 28, 2018

This should work, but you might want to test it on a small number of files first. The ideal location would be mmccarthy@thing2.marine.usf.edu:/thing2/imars-objects/big_bend/wv2/2014 and .../2015

@mjm8
Copy link
Collaborator

mjm8 commented Jun 28, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 28, 2018

Should be the same. can you ssh to thing2.marine.usf.edu?

@mjm8
Copy link
Collaborator

mjm8 commented Jun 28, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jun 28, 2018

Ah, okay. I guess it is not working. Noted.

Use mmccarthy@seashell.marine.usf.edu:/srv/imars-objects/big_bend/wv2/2014 then.

It will end up the in the same place, just a bit more network usage.

@mjm8
Copy link
Collaborator

mjm8 commented Jun 28, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jul 17, 2018

How go the transfers?

@mjm8
Copy link
Collaborator

mjm8 commented Jul 17, 2018 via email

@7yl4r
Copy link
Member Author

7yl4r commented Jul 17, 2018

I just fixed an issue that was killing 2/3 of the jobs. You can check on the running jobs in airflow here, and the output files are being saved to /srv/imars-objects/big_bend/tif_r_rs_wv2/. It looks like the permissions aren't right. I will fix that soon as well.

@7yl4r 7yl4r closed this as completed Jul 26, 2018
7yl4r added a commit to USF-IMARS/imars-etl that referenced this issue Dec 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants