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

position_from_velocity in parallel so that it integrates from the starting lat/lon position of each trajectory? #421

Open
selipot opened this issue Apr 25, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@selipot
Copy link
Member

selipot commented Apr 25, 2024

How would you use position_from_velocity in parallel so that it integrates from the starting lat/lon position of each trajectory? This would imply passing x_origin and y_origin of size rowsize but right now the function only accepts floats ... That's a ragged array problem for clouddrift! @kevinsantana11

Originally posted by @selipot in #180 (comment)

@selipot selipot changed the title By the way, how would you use position_from_velocity in parallel so that it integrates from the starting lat/lon position of each trajectory? This would imply passing x_origin and y_origin of size rowsize but right now the function only accepts floats ... That's a ragged array problem for clouddrift! @kevinsantana11 position_from_velocity in parallel so that it integrates from the starting lat/lon position of each trajectory? Apr 25, 2024
@selipot selipot added the enhancement New feature or request label Apr 25, 2024
@philippemiron
Copy link
Contributor

philippemiron commented Apr 26, 2024

I see the problem now. And I think we already discussed this at one point...

The idea would be to add the possibility of passing a special *arg and **kwarg that would be a list of len(rowsize). That way we could pass different arguments for each trajectory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants