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

Make print statements more informative for future debugging #7

Open
atteggiani opened this issue Jul 26, 2024 · 0 comments · May be fixed by #55
Open

Make print statements more informative for future debugging #7

atteggiani opened this issue Jul 26, 2024 · 0 comments · May be fixed by #55
Assignees

Comments

@atteggiani
Copy link
Collaborator

Print statements are printing just variable values (e.g. print(f.lbuser4, f.lblev, f.lblrec, f.lbhr, f.lbcode)).
It would be good if they print more information to help future debugging.

@atteggiani atteggiani moved this to Parked 🅿️ in ACCESS-RAM3 Jul 26, 2024
@atteggiani atteggiani moved this from Parked 🅿️ to New Issues in ACCESS-RAM3 Jul 26, 2024
@atteggiani atteggiani moved this from New Issues to Todo ⏳ in ACCESS-RAM3 Jul 28, 2024
@atteggiani atteggiani self-assigned this Aug 2, 2024
@atteggiani atteggiani linked a pull request Feb 24, 2025 that will close this issue
10 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Todo ⏳
Development

Successfully merging a pull request may close this issue.

1 participant