Feature request
Alternative or maybe complimentary to #358. When trying to get a complicated function working via batch, it can be difficult to debug due to dask error logs encasing the actual function failure. One helper function that could be useful is a try_batch or test_batch function, which operates identically to batch, but instead takes a random lightcurve (or optionally a specific lightcurve), computes it, and then tries the function call on that lightcurve. This would allow a user to tinker with the exact output of their function and see failure states without needing to fight with Dask.
Before submitting
Please check the following:
[ ] I have described the purpose of the suggested change, specifying what I need the enhancement to accomplish, i.e. what problem it solves.
[ ] I have included any relevant links, screenshots, environment information, and data relevant to implementing the requested feature, as well as pseudocode for how I want to access the new functionality.
[ ] If I have ideas for how the new feature could be implemented, I have provided explanations and/or pseudocode and/or task lists for the steps.
Feature request Alternative or maybe complimentary to #358. When trying to get a complicated function working via batch, it can be difficult to debug due to dask error logs encasing the actual function failure. One helper function that could be useful is a
try_batchortest_batchfunction, which operates identically to batch, but instead takes a random lightcurve (or optionally a specific lightcurve), computes it, and then tries the function call on that lightcurve. This would allow a user to tinker with the exact output of their function and see failure states without needing to fight with Dask.Before submitting Please check the following: