Zero space status during processing
A widely used tool for visual exploration of scientific literature.
Brought to you by:
citespace
Menu
▾
▴
Dear Professor Chen,
I experience a problem processing files in Citespace. When I set up the project and click "Go", Process Reports do show the progress, however, Space Status shows zeros. In the end of process, there is no "visualize" option, only general stats. The problem persists for all project that I have created in Citespace as well for any new ones. Could you please suggest a potential solution?
Best regards,
Glib Voloskyi
Last edit: Glib Voloskyi 2021-08-03
It seems something wrong with the data files. Can you upload the first 2 data files shown in the Untitled1.jpg?
Sure. Please find them here.
Though I am not sure if the problem is the dataset. I could process it previously. And all other datasets that worked fine have the same error now.
Last edit: Glib Voloskyi 2021-08-04
Just tested the 2 files with 5.8.R1 (built July 18, 2021), but it ran smoothly and didn't give any erros (see attached). Let me know the version and the built date of the version you are using.
Last edit: Chaomei Chen 2021-08-04
It is 5.8.R1 from July 18, 2021
I noticed you have 32-bit Java, but that shouldn't be the problem. Can run the Demo project and see if that has any problems.
I haven't had Demo projects, so I had to reinstall Citespace to have them back. I tried it previously, and it didn't help. But this time, I also deleted citespace,project.txt and the .citespace folder from my user folder. It worked! The problem disappeared for now.
Thank you for your help
Thanks. It is good to know. On the other hand, perhaps just rename the citespace.project.txt instead of deleting it since it contains your existing projects and you may need some of them. Keep a renamed copy to make it easier to restore any projects from the past (just cut and paste to the new file).
Certainly.
I also looked deeper into an error, and here is what I have found: an error is a result of an irrelevant percentage of nodes to the label value. In particular, I used the % sign that seems to be a source of the problem (screenshot 1). Once I changed the value, the problem disappeared, which is, of course, a much more elegant solution than getting rid of a project file.