Skip to content

docs: add Dynamic Foraging Behavior V2 pipeline - #213

Merged
arjunsridhar12345 merged 2 commits into
mainfrom
212-add-dynamic-foraging-behavior-only-v2-pipeline-to-docs
Sep 4, 2026
Merged

arjunsridhar12345 merged 2 commits into
mainfrom
212-add-dynamic-foraging-behavior-only-v2-pipeline-to-docs

Conversation

@arjunsridhar12345

@arjunsridhar12345 arjunsridhar12345 commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Attempts to close #212


📚 Documentation preview 📚: https://scicomp-docs--213.org.readthedocs.build/en/213/

@dougollerenshaw

Copy link
Copy Markdown
Contributor

Before approving, I'm a bit apprehensive to refer to it as the "Dynamic Foraging Behavior V2" pipeline. Are you using "V2" to identify it as being compliant with v2 metadata schema? If so, I don't think that's the right choice because presumably we'll continue to keep this pipeline up to date with future metadata schema versions as opposed to making new pipelines. I don't think the pipeline should be named for the metadata schema.

The associated repo is just called the "dynamic-foraging-processing-pipeline" To me, that is a more sensible name. Once the legacy pipeline is deprecated, there will just be a single Dynamic Foraging pipeline, right? Though until that happens, I can see how this will continue to be confusing.

What do you think makes the most sense here?

@arjunsridhar12345

Copy link
Copy Markdown
Contributor Author

Before approving, I'm a bit apprehensive to refer to it as the "Dynamic Foraging Behavior V2" pipeline. Are you using "V2" to identify it as being compliant with v2 metadata schema? If so, I don't think that's the right choice because presumably we'll continue to keep this pipeline up to date with future metadata schema versions as opposed to making new pipelines. I don't think the pipeline should be named for the metadata schema.

The associated repo is just called the "dynamic-foraging-processing-pipeline" To me, that is a more sensible name. Once the legacy pipeline is deprecated, there will just be a single Dynamic Foraging pipeline, right? Though until that happens, I can see how this will continue to be confusing.

What do you think makes the most sense here?

agree, keeping it the same name as the repo is the most sensible I think. I used v2 to imply the metadata but also the fact that its a new acquisition system which can also be confusing, but that's covered in the pipeline readme so I think it makes sense to do what you suggested and just use the sensible name (the name of the repo - dynamic-foraging-processing-pipeline)

@dougollerenshaw

Copy link
Copy Markdown
Contributor

Sounds good. Hopefully we can get the old pipeline shut off soon so there will truly be just one Dynamic Foraging pipeline.

@arjunsridhar12345

Copy link
Copy Markdown
Contributor Author

looking at the read the docs page here

{27055888-0883-402E-A6F3-3DC1B92A954E}

Should the name then just be Dynamic Foraging Behavior like the other ones?

@dougollerenshaw

Copy link
Copy Markdown
Contributor

looking at the read the docs page here

{27055888-0883-402E-A6F3-3DC1B92A954E}

Should the name then just be Dynamic Foraging Behavior like the other ones?

I think that makes a lot of sense. It's consistent with the others, and it also implicitly disambiguates it from the legacy pipeline since the legacy pipeline handled both behavior and FIP, whereas this name makes it clear that it's behavior-only.

@dougollerenshaw dougollerenshaw left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@arjunsridhar12345
arjunsridhar12345 merged commit 4c67179 into main Sep 4, 2026
1 check passed
@arjunsridhar12345
arjunsridhar12345 deleted the 212-add-dynamic-foraging-behavior-only-v2-pipeline-to-docs branch September 4, 2026 21:52
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

Successfully merging this pull request may close these issues.

Add dynamic foraging behavior only v2 pipeline to docs

2 participants