Releases: rjdverse/rjdemetra
RJDemetra 0.2.7
NEWS
-
URL to github repository updated (github.com/jdemetra replaced by github.com/rjdverse).
-
results of
user_defined_variables()
updated. -
README correction.
-
benchmarking option added to
x13_spec()
andtramoseats_spec()
and in output ofx13()
andtramoseats()
. -
.jars updated.
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
, andi_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 parametercomponent
. -
some corrections in
print()
methods.
RJDemetra 0.2.4
NEWS
-
New function
get_all_names()
andget_position()
. -
correction of
save_workspace()
andload_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
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, useoptions(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 incomplete_dictionary.SA
) when a userdefined variable was already in the workspace but with a different suffix.