RJDemetra 0.2.6

NEWS

• possibility to export last msr for monthly data (issue #122).

• possibility to export X-11 some components: y_cmp, y_cmp_f, t_cmp, t_cmp_f, sa_cmp, s_cmp, s_cmp_f, and i_cmp.

• correction when importing models containing ramp regressors when the frequency is not 12 (monthly).

• correction of get_jmodel() with empty multiprocessings.

RJDemetra 0.2.5

NEWS

• proc_data() update to export more data from Java object.

• seasonality Kurskal-Wallis test corrected (issue #128).

• vcov() correction when matrix NULL and new parameter component.

• some corrections in print() methods.

RJDemetra 0.2.4

NEWS

• New function get_all_names() and get_position().

• correction of save_workspace() and load_workspace() when using relative path.

RJDemetra 0.2.3

NEWS

• Typo in printed arima coefficients : BPhi and Theta were inverted.

RJDemetra 0.2.2

NEWS

• update documentation

• removes extra argument print tramo

• SystemRequirements update for CRAN policies

RJDemetra 0.2.1

NEWS

• Fix complete_dictionary.SA() to avoid warning.

RJDemetra 0.2.0

NEWS

• Bug with x11 introduced in RJDemetra 0.1.9 (issue #99).

• Java 17 compatibility.

• Change of javanamespace to avoid name clashes with jd+ 3.0.

• easter.enabled not working since RJDemetra 0.1.9.

• Default parameters of the span specification d0 and d1 as NA for clarity (issue #102).

RJDemetra 0.1.9

NEWS

• Easter specification was not working.

• Some typo in the documentation.

• Java version restriction: JDemetra+ and RJDemetra are not compatible with Java 16 and higher. The compatibility with those versions of Java will be possible from next release of JDemetra+. Documentation harmonization : only Java JRE is needed.

• java_ncore option added to limit the number of cores used in Java to two to be sure to respect CRAN policies (to remove the option, use options(java_ncore = NULL)). However, it should not be necessary since RJDemetra shouldn't use multithread (issue #89).

RJDemetra 0.1.7

NEWS

• Data updated until December 2020.

• Fixed coefficients with user-defined calendar regressors can now correctly be used (issue #87).

• There was an error in add_sa_item (more precisely in complete_dictionary.SA) when a userdefined variable was already in the workspace but with a different suffix.

RJDemetra 0.1.6

Bug fixed

• x11.seasonalma argument wasn't taken into account (issue #78).

• ipi_c_eu updated: the previous data were calendar adjusted data, they are now unadjusted (neither seasonally adjusted nor calendar adjusted data).

• the print result of the combined test was incorrect.