-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when reading database #12
Comments
Hi @weilinleee, there is an issue with |
Hi @mengqi-z, thanks for the update. However, the error is coming out again. I also try to set a working directory that is totally different from database directory, but is does not work either. |
Hi @weilinleee , would you please check if those GCAM .basex files are directly within this path: /Users/winnielee/Desktop/PLUTUS/IDBNexus? I figured sometimes unzipping the .zip file will create double-level folders where your .basex file may be located in /Users/winnielee/Desktop/PLUTUS/IDBNexus/IDBNexus. The Also, I see that you are running in code chunks. Some encountered problems when using code chunks to run |
Hi @Mengqi, I run the following code: Load required packageslibrary(plutus) Set your directory based on the example dataset locationworkdir <- 'C:/Users/carla/Desktop/GCAM53' provide path to the desired GCAM database folder that holds .basex files.path_to_gcamdatabase <- file.path(workdir, 'IDBNexus_gcam5p3_HadGEM2-ES_rcp8p5') Use plutus::gcamInvest to calculate stranded assets and electricity investmentsinvest <- plutus::gcamInvest(gcamdatabase = path_to_gcamdatabase, I got a similar error to @weilinleee when reading the IDBNexus database. I have double checked that the GCAM .basex files are directly within the following path: C:/Users/carla/Desktop/GCAM53/IDBNexus_gcam5p3_HadGEM2-ES_rcp8p5 I am not running the code in chunks. Below is the error I got in the test.txt file that appeared after running the function: ########################################################################################## The following named parsers don't match the column names: name, date, version On the other hand, the function does not generate a dataProj.proj. I would appreciate if you could help me to solve this issue. Thanks. |
Hi @CarlaCamposM, I am sorry that you are experiencing the same problem related to In the meanwhile, if you would like to explore outputs from
|
Hi @mengqi-z
[1] "Connecting to GCAM database provided C:/Users/nurfi/Desktop/GCAM/output//database_basexdb..." From this, there are dataProj file and readGCAM folder in the designated folder. |
Hi @nurf-004, I think it is an issue related to More details related to this issue for Mengqi |
Hi @mengqi-z Thank you for your kind response. I have solved this issue finally. May I ask you some questions and your confirmation. First, I'm wondering the calculation process of annual electricity capacity installations and annual premature retirements. I'm trying to understand how the Plutus works when I look at the elec gen by gen tech and cooling and vintage in the ModelInterface (how do we calculate based on such information?). Second, if we want to modify the parameters (lifetime and steepness, and capacity factors), should we do it first before we run the GCAM (the input files, assuming we used given assumptions in GCAM) to get the datasets or after we generate the datasets (you mention: # gcamdataFile = path_to_gcamdataFile, # Use this argument if any data files has been updated). Maybe I misunderstood regarding the statement. Last, is there any differences between Class1 and Class2? The explanation is not clear enough for me. Thank you very much for your help! |
Hi @nurf004 , Thank you for your questions.
|
Hi @mengqi-z Noted. Thank you very much for answering my questions. |
I try to follow the case tutorial and read database IDBNexus downloaded from Github, but there is always an error saying that "Database does not exist or is invalid." ( I am pretty sure the path is correct.) I also try to read GCAM database provided by my colleague, but the error comes out all the time.
The text was updated successfully, but these errors were encountered: