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

Documentation of Resources #16

Open
sebastiandig opened this issue Jun 30, 2023 · 3 comments
Open

Documentation of Resources #16

sebastiandig opened this issue Jun 30, 2023 · 3 comments
Assignees

Comments

@sebastiandig
Copy link
Contributor

Hi @7yl4r

I'm not sure where to put resources for optics information/processing. It would probably just be a folder with different .md files for parameters. Some theory, videos, doucments, code, etc.

Let me know where I can start putting information, whether in dat-docs or another repo all together.

Best,
@sebastiandig

@7yl4r
Copy link
Member

7yl4r commented Jun 30, 2023

Once we get up over a handful of files a new repo makes more sense to me. I suggest you create it under USF-IMaRS and then add a link to the repo here.

@sebastiandig
Copy link
Contributor Author

I don't know specifically how many files we'll have, but for the time being, what would be easiest to do?
I think resources for cdom, filter pads, and reflectance would be a start.

If I do create another folder/repo, what do you think we should name it?

I think at some point it'll extend beyond just ocean color data. I think a place for resources would be helpful for new/old personnel.

@7yl4r
Copy link
Member

7yl4r commented Jul 4, 2023

I like breaking things out into many repos. A repo that links out to each of the parts can always be made. This repo is meant to be the entry point for all data questions with many links out to other locations.

I think you are more qualified to guess at the naming and organization questions. We can always move and rename later. If this is for optics processing, then USF-IMARS/optics_processing will work for now. My strategy is to organize however you like and include a README.md explaining your organizational rationale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants