You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using fluxible to process data recently taken in Australia. We have an ideal flux window of 2 minutes, but in the most recent campaign we had to cut several of our measurements short due to clouds moving in. It would be helpful if flux_match could accept a column of measurement lengths rather than just a single number. An alternative workaround would be if the user could specify an end column.
The text was updated successfully, but these errors were encountered:
I'm using
fluxible
to process data recently taken in Australia. We have an ideal flux window of 2 minutes, but in the most recent campaign we had to cut several of our measurements short due to clouds moving in. It would be helpful ifflux_match
could accept a column of measurement lengths rather than just a single number. An alternative workaround would be if the user could specify an end column.The text was updated successfully, but these errors were encountered: