jonghyunharrylee / pyPCGA

pyPCGA: fast and scalable inverse modeling approach
BSD 3-Clause "New" or "Revised" License
23 stars 15 forks source link

add post-processing notebook for red river inset example #3

Closed mfarthin closed 6 years ago

mfarthin commented 6 years ago

We could also turn the plot_red_inset.py script into a jupyter notebook.

jonghyunharrylee commented 6 years ago

Also I have plot_along_channel_red_inset.py for crosssectional plots.. I will incorporate it later

mfarthin commented 6 years ago

Yeah, I will try to add those if I get some time this weekend.

Do you want me to add some of the input descriptions and such to the stwave notebook too?

jonghyunharrylee commented 6 years ago

Yes, you can add that. What kind script did you use to identify input parameters? Not sure you explained PCGA input parameters manually. I wanted to use stwave python wrapper (you sent me before right?) instead of the current adhoc input/output processing and stwave execution script, but hasn't had time for it.

mfarthin commented 6 years ago

Well, I just entered them manually. If there were a place where the descriptions were,  I could  probably write a script to populate the table  automatically.  Maybe adding the other wrapper would be good for me and Matthew Geheran to do.  It would give him a chance to get more familiar with pcga too. 

Sent from my Verizon, Samsung Galaxy smartphone -------- Original message --------From: Harry Lee notifications@github.com Date: 2/8/18 7:24 PM (GMT-06:00) To: jonghyunharrylee/pyPCGA pyPCGA@noreply.github.com Cc: mfarthin mwfarthing@gmail.com, Author author@noreply.github.com Subject: Re: [jonghyunharrylee/pyPCGA] add post-processing notebook for red river inset example (#3) Yes, you can add that. What kind script did you use to identify input parameters? Not sure you explained PCGA input parameters manually. I wanted to use stwave python wrapper (you sent me before right?) instead of the current adhoc input/output processing and stwave execution script, but hasn't had time for it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/jonghyunharrylee/pyPCGA","title":"jonghyunharrylee/pyPCGA","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/jonghyunharrylee/pyPCGA"}},"updates":{"snippets":[{"icon":"PERSON","message":"@jonghyunharrylee in #3: Yes, you can add that. What kind script did you use to identify input parameters? Not sure you explained PCGA input parameters manually. I wanted to use stwave python wrapper (you sent me before right?) instead of the current adhoc input/output processing and stwave execution script, but hasn't had time for it. "}],"action":{"name":"View Issue","url":"https://github.com/jonghyunharrylee/pyPCGA/issues/3#issuecomment-364305895"}}}

mfarthin commented 6 years ago

Pull request #6 provides a first cut for the post-processing notebook