JGCRI / gcam-core

GCAM -- The Global Change Analysis Model
http://jgcri.github.io/gcam-doc/
Other
272 stars 162 forks source link

Issue in running driver to create XMLs via GCAM v5.4 release package #213

Open ankurmalyan opened 2 years ago

ankurmalyan commented 2 years ago

Hi,

I recently downloaded the GCAM v5.4 release package in a new windows system. Installed all required updated packages in R to process the datasystem.

However, While running driver() or driver(write_output=FALSE, write_xml=TRUE), I am getting following error:

[1] "module_emissions_L103.ghg_an_USA_S_T_Y" [1] "- make 0.13" [1] "module_emissions_L105.nh3_an_USA_S_T_Y" [1] "- make 0.19" [1] "module_emissions_L152.MACC" Error in left_join_error_no_match(., EPA_MACC_control_mapping, by = c("sector", : left_join_no_match: NA values in new data columns

My guess is that it is being caused because of some incorrect package that is not compatible with the codes. It would be great if compatible package versions could be shared or some guidance on resolving this issue can be provided.

Following is my sessioninfo():

R version 4.2.0 (2022-04-22 ucrt) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 10 x64 (build 22000)

Matrix products: default

locale: [1] LC_COLLATE=English_India.utf8 LC_CTYPE=English_India.utf8
[3] LC_MONETARY=English_India.utf8 LC_NUMERIC=C
[5] LC_TIME=English_India.utf8

attached base packages: [1] stats graphics grDevices utils datasets methods
[7] base

other attached packages: [1] gcamdata_5.1

loaded via a namespace (and not attached): [1] Rcpp_1.0.8.3 rstudioapi_0.13 magrittr_2.0.3
[4] hms_1.1.1 bit_4.0.4 tidyselect_1.1.2 [7] R6_2.5.1 rlang_1.0.2 fansi_1.0.3
[10] dplyr_1.0.8 tools_4.2.0 vroom_1.5.7
[13] data.table_1.14.2 utf8_1.2.2 cli_3.2.0
[16] withr_2.5.0 ellipsis_0.3.2 bit64_4.0.5
[19] assertthat_0.2.1 tibble_3.1.6 lifecycle_1.0.1
[22] crayon_1.5.1 purrr_0.3.4 readr_2.1.2
[25] tzdb_0.3.0 tidyr_1.0.2 vctrs_0.4.1
[28] glue_1.6.2 stringi_1.7.6 compiler_4.2.0
[31] pillar_1.7.0 generics_0.1.2 pkgconfig_2.0.3

Thanks a lot.

russellhz commented 2 years ago

Hi @ankurmalyan, the usual suspects for these problems are tidyr and readr. It looks like the tidyr version is ok, so I would suggest reverting readr back to 1.4.0.