Fix broken execution in Lightcurve tutorial (Issue #802)

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!

[Alisha1701]

"Wrapped the intentional failure in Lightcurve tutorial.ipynb with a try-except block to allow automated testing to complete successfully."

[matteobachetti]

Hi @Alisha1701, the cell has the tag raises-exception, that usually makes the notebook run despite the failure. Have you seen some instance where the notebook was interrupted by the exception?

[Alisha1701]

Hi @matteobachetti, thanks for pointing that out!

You are right—I noticed that the subsequent cells did execute correctly, but I wasn't aware that the raises-exception tag was handling that control flow.

My main motivation for the try-except block was to clean up the visual output. I thought that leaving a raw error traceback (the red text) in the documentation might look 'broken' or confusing to a new user reading the tutorial.

If you prefer keeping the raw error visible to demonstrate the failure mode, I am happy to close this PR. But if you agree that hiding the traceback improves readability, I'm happy to keep it. Let me know what you prefer!