 |
|
|
|
|
|
|
|
FAQ
|
- Why does TIMESAT 3.1.1 not work with Matlab 2014b?
There were many changes in Matlab 2014b making TIMESAT 3.1.1. incompatible with this version. They are fixed in version 3.2.
- What platforms and operating systems are supported?
TIMESAT 3.2 was developed with Matlab 2012b and 2014b under Windows 7 (64 bit), and Linux CentOS (64-bit). TIMESAT 3.1 was developed on Matlab R2010b under Windows XP (32-bit) and Linux CentOS (64-bit). Fortran programmes were compiled with Intel Fortran parallel studio XE 2011.
- What are the major changes between version 3.2, 3.1, 3.0 and version 2.3?
For details please see the text under "Software versions".
- How can I convert my images to a format that suits TIMESAT?
This is a common question, but we do not have the capacity to maintain information about format conversion from different image processing or GIS packages. Instead we have selected to work with the most generic type of formats, flat binary files, which is supported by most software packages. Please see the text under "File formats" for some more information.
- Some data are missing from my time series - can I still run TIMESAT?
TIMESAT requires an equal number of data files each year (or in the case of data in ASCII file equal number of data values). If an image is missing for a certain date it is necessary to add an image for this date containing a code for missing data (e.g. -999) for each pixel. When running TIMESAT the data range is then specified so that it excludes this missing value. When running from an ASCII file a missing data value can just be added to the list of data values at the correct position. TIMESAT uses least-squares fits that can cope with a certain number of missing data values in a time-series. However, the processing will skip to the next pixel if too many missing data values are encountered.
- I have two years of data but I only get one season in the output from TIMESAT?
TIMESAT will always generate one less season than the number of years of data. This is because one calendar year may not always contain one full growing season (e.g. if the season begins in December and ends in October). TIMESAT will start to process the first full season encountered, continuing until the end of the data set, and generate n-1 seasons. If a user wants to process one particular year it is necessary to surround this year with data on both sides. Thus, a minimum of three years of data is needed to make sure that a comprehensive picture of the phenology in the middle year is generated. If no data files exist for years before and after the time-period to be processed we recommend the user to duplicate the first and last years of data and add first and last in the time series. We have added a section in the new users manual to clarify this point.
- Why do I get large areas containing only missing data, when I process my TIMESAT output with seas2img?
This may occur if you have not specified a time interval wide enough to include the full growing season in seas2img. The interval sometimes needs to be very wide, perhaps spanning one and a half years. Try widening the interval and see if you obtain data for all your area. Another reason may be that the original data is too noisy for TIMESAT to identify any meaningful sesons in your areas. You can distinguish these cases by setting separate missing value codes in seas2img.
- Does TIMESAT run under all operating systems and Matlab versions?
No, see above for operating systems supported. We have not systematically tested other combinations of Windows and Matlab. However, there seem to be some problems connected with different language versions. Unfortunately we do not have the capacity to handle these problems.
- Errors occur when executing TIMESAT using the Matlab Compiler Runtime (MCR).
Several users have reported problems with the TIMESAT MCR version. We are unable to answer most of these questions, however, we occasionally get useful hints from our users.
Antoine Denis reported the following:
MCR has installed OK, but when launching TIMESAT.exe the following message appeared:
"Error: Could not access the MCR component cache."
The component cache is a folder located in a directory like: "C:\Users\username\AppData\Local\Temp\username\ mcrCache7.14", and may for some reason become corrupted. Denise suggests the following:
Go to the directory "C:\Users\username\AppData\Local\Temp\username\ mcrCache7.14".
Simply give a new name to the "mcrCache7.14" folder like "old_mcrCache7.14"
Launch “TIMESAT.exe” by clicking on it (in the folder "…\TIMESAT\timesat311_standalone_windows32\timesat311\compiled\Win32)"
This will automatically recreate a working "mcrCache7.14" folder in the directory "C:\Users\username\AppData\Local\Temp\username\ mcrCache7.14".
TIMESAT should now open normally.
We thank Antoine and hope this will be useful also to other users.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Web design: Dr Maggie
|
|
Site maintained by: Lars Eklundh.
This page updated: 28 April 2015
|
|
|
