Needed content

[RobHolman]

What new content do people feel that we need? I can't recall if we have much on merges and rectifications. I know that I plan to do something with vBar soonish. What else is missing?

[SRHarrison]

Hi Rob,
I'd love to learn more about merges. I've done them before outside of Argus code structure by blending two individual rectifications with tapered masks... But, looking through the CIL's merge2 stuff is pretty confusing - especially without the DB stuff to know what's being passed in all the structures.

I would love to know more about the existing multi-camera station tools. UAV-toolbox is great for single cameras (fixed and UAV), but it would still be helpful to gain perspectives on how you tackled the multi-camera issues. I suspect that CIL tools must have thought of everything already and has loads of cool tools, but for people unfamiliar with the package it's hard to know how to proceed. I frequently write my own code to do something, then soon realize that you already had a tool for that and you did it much better.

vBar.

I'm still curious what goes on in the Argus Database (DB). Is that something that I should try to make my camera stations utilize? Can I get away with my own .mat version of a DB? After how many stations does it become practical to use this method?

[RobHolman]

I’m certainly supportive of these next steps in knowledge dissemination. This raises the question of how best to do that. Maybe that could be the next Argus 201 boot camp? I’m happy to explain everything about what we do but I’d like to do it efficiently and with a record. Have others thought about next steps. A high priority is to have a gathering of geeks. YHS Rob Holman SECNAV/CNO Chair in Oceanography 104 Ocean Admin Bldg. CEOAS-OSU Corvallis, Oregon, USA 97331-5503 ph: 1-541-737-2914 [email protected] http://cil-www.coas.oregonstate.edu

…

On Oct 5, 2017, at 10:16 AM, Shawn Harrison ***@***.***> wrote: Hi Rob, I'd love to learn more about merges. I've done them before outside of Argus code structure by blending two individual rectifications with tapered masks... But, looking through the CIL's merge2 stuff is pretty confusing - especially without the DB stuff to know what's being passed in all the structures. I would love to know more about the existing multi-camera station tools. UAV-toolbox is great for single cameras (fixed and UAV), but it would still be helpful to gain perspectives on how you tackled the multi-camera issues. I suspect that CIL tools must have thought of everything already and has loads of cool tools, but for people unfamiliar with the package it's hard to know how to proceed. I frequently write my own code to do something, then soon realize that you already had a tool for that and you did it much better. vBar. I'm still curious what goes on in the Argus Database (DB). Is that something that I should try to make my camera stations utilize? Can I get away with my own .mat version of a DB? After how many stations does it become practical to use this method? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.

[mpalmsten]

In my experience, the setting up the full database and Argus toolbox are essential for a multi-camera system. It takes a little time, but is not complicated to do.

I've compiled a SOP that Jenna and I have used to set up our own versions of the Argus DB for use with our cameras. I'm happy to share.

[SRHarrison]

Yes please! *Shawn Harrison**U.S. Geological Survey* Pacific Coastal and Marine Science Center Santa Cruz, CA 95060 Office: (831) 460-7549 Mobile: (720) 737-0131 Email: [email protected]

…

On Wed, Nov 1, 2017 at 9:53 AM, mpalmsten ***@***.***> wrote: In my experience, the setting up the full database and Argus toolbox are essential for a multi-camera system. It takes a little time, but is not complicated to do. I've compiled a SOP that Jenna and I have used to set up our own versions of the Argus DB for use with our cameras. I'm happy to share. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#24 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AVa07ej8jwYrBJ0eliNmNh8hQR-bX7oLks5syKH-gaJpZM4NK1A9> .

[RobHolman]

I think I am responding right by doing this by email. The one thing we should think carefully about is have clear agreement on what goes into the database tables. About 20 years ago Nathaniel and the Europeans also set up a local version of a database that diverged completely from the traditional Argus one, a problem that eventually took many months of labor to fix. I think the main thing is agreement on content of tables, which is why I introduced the geek discussion recently. Sounds like I should be more proactive with this. If we agree on table content we should be fine. YHS…Rob Rob Holman SECNAV/CNO Chair in Oceanography 104 Ocean Admin Bldg. CEOAS-OSU Corvallis, Oregon, USA 97331-5503 ph: 1-541-737-2914 [email protected] http://cil-www.coas.oregonstate.edu

…

On Nov 1, 2017, at 9:53 AM, mpalmsten ***@***.***> wrote: In my experience, the setting up the full database and Argus toolbox are essential for a multi-camera system. It takes a little time, but is not complicated to do. I've compiled a SOP that Jenna and I have used to set up our own versions of the Argus DB for use with our cameras. I'm happy to share. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.