Skip to content
Snippets Groups Projects

fixing writeOutput for observation_trends

Fixing a bug that I introduced in 2021

Merge request reports

Pipeline #10376 passed

Pipeline passed for 2363e25d on MichelJuillard:observation_trends_fix

Closed by MichelJuillardMichelJuillard 1 year ago (Apr 24, 2024 7:34pm UTC)

Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • added bug label

  • It seems that this behaviour has been there for a very long time (it’s been like this at least since we switched to git).

    Note that this cannot be merged without adapting the MATLAB code accordingly, because the latter expects a string and evaluates it (see for example line 43 of matlab/compute_trend_coefficients.m). Otherwise several tests will fail (e.g. fs2000/fs2000a.mod). Do you plan to work on the corresponding merge request for the MATLAB code?

    Also note that, for consistency, if we decide to apply this change, it should also be made to deterministic_trends.

  • I have an example that works with the stable version but not with the unstable one. Let me compare with the fs2000a.mod to understand what is going on. I have no intention or need to modify the MATLAB code.

  • To say it otherwise, I don’t understand why you say there is a bug. The MATLAB code works fine with the preprocessor as it currently is, and no longer works with your proposed change.

    So it looks to me that you are rather suggesting a change in the implementation, which indeed looks like an improvement because I don’t understand why the expression is currently passed as a string and is later evaluated. But if you want to make this change, it has to be done consistently throughout the MATLAB code (and also with deterministic_trends).

    Edited by Sébastien Villemot
  • Most likely I made a wrong diagnostic on a problem that I encountered

  • The problem was in the *.mod file.

  • closed

Please register or sign in to reply
Loading