FAQ or Frequently Asked Questions


Here is a selection of the questions other users stumbled upon more than once...


  1. Q: The processing stops after the flux-partitioning has finished but I am not redirected to the results page. The logo keeps on spinning, what can I do?
    A: There are several possible reasons for this. Most likely, if you had selected both flux-partitioning methods, the processing might have stopped during the GL2010 flux-partitioning. In this case, please re-submit your query, indicating only standard flux-partitioning (i.e., GL2010=NO). This is one of the new features we have included in early 2012. If your query still doesn't finish, please contact us for further support.
  2. Q: The processing stops at 'Summary generation started' and does not move any further. What could be the reason?
    A: This problem occured repeatedly in data sets with little available data due to problems in the artificial gap scenarios. We have worked on a fix for this and you are very welcome to try the according data sets which did not seem to work before again now with the updated version of the tool.
  3. Q: I am very keen to use your fantastic gap filling tool, but i am having problems. I have attached my data file, and also the sample data file that i downloaded from your website. I haven't had any success with either file, and have not even been able to get to the log file or a page saying what the problem is. What am i doing wrong?
    A: This is the scenario when our processing server is not working. We are trying hard to maximize the availability of the tool for your convenience, however, sometimes the tool is not working properly due to maintenance or unexpected behavior of our servers at the Max Planck Institute.
  4. Q: I would like to process a big data set with several years of data (e.g., 8 years) in one file. After a while, the processing stops for no certain reason. What can I do?
    A: We still have only limited experiences with processing several years of data at once. There are several sources of error here including memory problems and other limitations of our processing routines. This will be addressed in the future by converting the source code into R, while demand is growing with the increase in temporal ranges of Eddy data. As of now, the rule of thumb is to partition your data set into smaller chunks of data, e.g. 1 or 2 years maximum per input file and then process all of them separately.
  5. Q: Why is there no DataSetafterGapfill.txt output file anymore for flux-partitioning jobs?
    A: This file has been removed to save memory, for flux-partitioning jobs all the output variables are now to be found in DataSetafterFluxpart.txt or DataSetafterFluxpartGL2010.txt.
  6. Q: Why is Reco missing in the flux-partitioning output?
    A: Good question! Meanwhile we have fixed this and Reco is now included in the result files for your convenience.
  7. Q: Recently, uncertainty estimates have been added to the functionality of the tool - where do I find them and how are they calculated?
    A: In the column with an _fs are the standard deviations of the according values used for gap-filling. E.g., NEE_fs for all the gaps. Additionally, columns with an _unc contain the standard deviations for all measurements, including values that actually aren't a gap. They are calculated by simulating a gap and applying the standard gap-filling procedure. Please also refer to the Methods section or Reichstein et al. 2005.

If your problem could still not be resolved by now, do not hesitate to contact us.
When emailing us for support, please also attach the infolog.txt of your job to your email.