Display IssueTB, IssuesTB or SelectorTB with formatted output in the console
# S3 method for class 'IssueTB'
print(x, ...)
# S3 method for class 'IssuesTB'
print(x, ...)
# S3 method for class 'SelectorTB'
print(x, ...)
# S3 method for class 'summary.IssueTB'
print(x, ...)
# S3 method for class 'summary.IssuesTB'
print(x, ...)
# S3 method for class 'LabelsTB'
print(x, ...)
# S3 method for class 'summary.LabelsTB'
print(x, ...)The object x invisibly.
This function displays an issue (IssueTB object), a list of issues
(IssuesTB object) or a list of selectors (SelectorTB objects) with
a formatted output.
issues_selector <- init_selector(
source = "Local",
file = file.path(
system.file("data_issues", package = "IssueTrackeR"),
"list_issues.yaml"
)
)
all_issues <- get_issues(selector = issues_selector)
#> The issues will be read from /home/runner/work/_temp/Library/IssueTrackeR/data_issues/list_issues.yaml.
# Display one issue
print(all_issues[1, ])
#>
#> ── Issue jdemetra/jdplus-main#1058 ──
#>
#> Title: Friedman Test function calls QS Test in SeasonalityTests
#> Text:
#> https://github.com/jdemetra/jdplus-main/blob/c91573b85827831899e58ee1c89a6a1cb8760a7e/jdplus-main-base/jdplus-sa-base-parent/jdplus-sa-base-api/src/main/java/jdplus/sa/base/api/diagnostics/SeasonalityTests.java#L58-L60
#>
#> Hi, I just noticed that in this file the friedmanTest function actually calls the QS test. I'm assum
#> ...
#>
# Display several issues
print(all_issues[1:10, ])
#> There are 10 issues.
#>
#> ── Issue jdemetra/jdplus-main#1058 ──
#>
#> Title: Friedman Test function calls QS Test in SeasonalityTests
#> Text:
#> https://github.com/jdemetra/jdplus-main/blob/c91573b85827831899e58ee1c89a6a1cb8760a7e/jdplus-main-base/jdplus-sa-base-parent/jdplus-sa-base-api/src/main/java/jdplus/sa/base/api/diagnostics/SeasonalityTests.java#L58-L60
#>
#> Hi, I just noticed that in this file the friedmanTest function actually calls the QS test. I'm assum
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1049 ──
#>
#> Title: Different Default Thresholds for Combined Seasonality Test Between Versions 2.2.
#> Text:
#> We have noticed that the Combined Seasonality Test diagnostic is labelled differently across software versions. In version 2.2.4, the diagnostic is classified as Severe, whereas in version 3.7.1 it is classified as Good for the same series (see attached screenshot).
#> In version 3, the threshold values are no longer visi
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1039 ──
#>
#> Title: Older WS are read not correctly
#> Text:
#> I created a WS with the version **3.7.1** with 1 SA-Processing with 1 SA-Item with:
#>
#> - the series AirPassengers ([air.csv](https://github.com/user-attachments/files/30928390/air.csv))
#> - the specification:
#> - X13 RSA3
#> - 1 outliers (AO in 1956-08-01) in the estimation spec
#> - a basic span (series span) from 1949-01-0
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1029 ──
#>
#> Title: Seasonal component in X11 spec : if set to NO, no info displayed in GUI
#> Text:
#> HI ,
#>
#> in v 3.8.0 if seasonal component is unticked in the X11 part of the spec
#>
#> No information is diplayed in GUI
#>
#> <img width="246" height="62" alt="Image" src="https://github.com/user-attachments/assets/a57354d6-256f-4bac-aff8-fa68720aee74" />
#>
#> the estimation appears as invalid
#>
#> <img width="647" height="40" alt="I
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1028 ──
#>
#> Title: Lack of documentation regarding assignment of roots in SEATS
#> Text:
#> Hello,
#> I was working with a jsai item with an ARIMA model with regular order (3,1,0). The three regular autorregressive roots are one real (negative) and two complex. According to the SEATS documentation, the complex roots go to the seasonal or the transitory component, but JDemetra+ is allocating them in the trend com
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1023 ──
#>
#> Title: OpenSSF badge
#> Text:
#> I recently discovered the OpenSSF badge.
#>
#> I was wondering if it applied to JDemetra+. It’s a badge that recognises packages that follow open-source best practice.
#>
#> The link is https://www.bestpractices.dev/
#>
#> ── Issue jdemetra/jdplus-main#1006 ──
#>
#> Title: Benchmarking Results includes forecast observations beyond the input series
#> Text:
#> <img width="340" height="216" alt="Image" src="https://github.com/user-attachments/assets/cd77b619-d644-4d03-925e-6a858eeb3709" />
#>
#> While testing JDemetra+ 3.7.1, I noticed an unexpected behaviour in the **Benchmarking Results** output. The input series used in this example ends in **2025 Q1**. However, the table displ
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1004 ──
#>
#> Title: Outlier type and position are missing in Matrix |> Outliers
#> Text:
#> Related to cosa-tsa-shop/UserSupport#10
#>
#> In the section Matrix |> Outliers (from a SA-Processing), the version 2 and 3 differs by their presentation:
#>
#> - In version 2 we observe a column by outliers with type, position, coeff and T-Stats
#> - In version 3 we observe 2 columns by outliers with coeffs and T-Stats
#>
#> Is it poss
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#1002 ──
#>
#> Title: Fix warnings when running CLI with Java25+
#> Text:
#> When running with Java25+, the following warnings are displayed:
#>
#> **CLI**
#> ```
#> WARNING: A restricted method in java.lang.System has been called
#> WARNING: java.lang.System::loadLibrary has been called by org.fusesource.hawtjni.runtime.Library in an unnamed module (file:/C:/.../appassembler/lib/jansi-1.18.jar)
#> WARNING: Use
#> ...
#>
#>
#> ── Issue jdemetra/jdplus-main#989 ──
#>
#> Title: Fix parsing of legacy TS meta
#> Text:
#> Parsing of legacy TS meta fails on Java25+ with some regional settings (`-Duser.language=fr -Duser.region=BE`)
# Display a selector
print(issues_selector)
#> There is 1 selector.
#>
#> Selector n°1
#> source: local
#> file: /home/runner/work/_temp/Library/IssueTrackeR/data_issues/list_issues.yaml
# Display the summary of one issue
summary(all_issues[2, ])
#> ── Issue jdemetra/jdplus-main#1049 ──
#>
#> Labels:
#> State: 🟢 Open
#> Nb comments: 0
#>
#> Title: Different Default Thresholds for Combined Seasonality Test Between Versions 2.2.4 and 3.7.1
#> Text:
#> We have noticed that the Combined Seasonality Test diagnostic is labelled differently across software versions. In version 2.2.4, the diagnostic is classified as Severe, whereas in version 3.7.1 it is classified as Good for the same series (see attached screenshot).
#> In version 3, the threshold values are no longer visible and cannot be adjusted manually. Could you please clarify whether the default thresholds have changed between versions and which diagnostic label should be considered?
#>
#> <img width="674" height="492" alt="Image" src="https://github.com/user-attachments/assets/a15b2a38-d816-4aa4-bf13-3f415ff1d851" />
#>
#> <img width="773" height="456" alt="Image" src="https://github.com/user-attachments/assets/72172828-2d4a-478b-bb92-ba50c6fffb23" />
#>
# Display the summary of
summary(all_issues[1:10, ])
#> There are 10 issues.
#> - jdemetra/jdplus-main#1058 ✔ Completed
#> - jdemetra/jdplus-main#1049 🟢 Open
#> - jdemetra/jdplus-main#1039 ✔ Completed
#> - jdemetra/jdplus-main#1029 🟢 Open
#> - jdemetra/jdplus-main#1028 ✔ Completed
#> - jdemetra/jdplus-main#1023 🟢 Open
#> - jdemetra/jdplus-main#1006 🟢 Open
#> - jdemetra/jdplus-main#1004 🟢 Open
#> - jdemetra/jdplus-main#1002 ✔ Completed
#> - jdemetra/jdplus-main#989 ✔ Completed