June 22:
Hi Richa
Did you look at the stderr and stdout log files for fcm_make, as described in the next step of the JULES FLUXNET tutorial (step no. 14)? What do the log files say? There are also other files in the same log directory which might be useful to look at, if the stderr and stdout logs aren’t sufficient.
Patrick McGuire
June 22:
First time i tried to compile the suite it worked fine. But due to some internet issues i was not able to get the output as the compilation was not completed.
But the second time when i tried to compile the same suite it showed FCM failed and i have no idea how to resolve it.
If anyone has faced this issue please let me know.
Richa
June 22:
I don’t have access to sci1 hence i login into cylc account and access the suite. What is the solution to the problem?
Richa
June 22:
Hi Richa
You should definitely use cylc1 instead of sci1.
Patrick
June 22:
Hi Richa
Can you try to use vi or cat or emacs or whatever, to look at the log files in the directory mentioned in step 14 of the tutorial?
Patrick
June 22:
Hi Patrick,
I’m not running the tutorial (my own suite), but I get the following (which is what Richa is apparently getting when running the tutorial)
" [FAIL] preprocess.prop{file-ext.h} = .inc: bad name-space
[FAIL] preprocess.prop{fpp.defs} = SCMA BL_DIAG_HACK INTEL_FORTRAN: bad name-space"
Jonathan
June 22:
Hi Jonathan (and Richa):
Yes, I saw the email from you and responded about it already.
What is your suite number on JASMIN? If your permissions will allow me, then I can look at your log files, to see more details beyond these two ‘[FAIL]’ lines.
That’s what I was asking you and Richa to do for yourselves in my prior emails.
The message that Richa was showing from her log file from the GUI is not very useful. It is often better to look at the log files on the command line instead of in the GUI.
The ‘[FAIL]’ lines that you quote above on the surface suggest that it might possibly have something to do with the type of processor being used.
You can also compare your suite with my suite with this command:
diff -r ~pmcguire/roses/u-al752 ~/roses/u-al752
I just restarted my suite, and it passes the fcm_make step just fine.
Patrick
June 22
Hi Patrick
The suite I am working on is u-al752. I shall see once the difference with the command as you have given in the following mails. Let me check.
Richa