Changes between Version 26 and Version 27 of FAQ


Ignore:
Timestamp:
Feb 27, 2013, 11:50:18 AM (6 years ago)
Author:
sick
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v26 v27  
    22 
    33== SonoView shows traces but HypoLine not == 
    4 >> Probably the trace and channel names of the header are not in the schema SxC SZ, SxC SE, SxC SN, SxW SZ, SxN SZ, SxE SZ where x is a number between 1-9. If you have no SNS station architecture try to create copies of existing traces and name them accordingly.[[BR]] 
    5 >> Another problem can be that the individual traces are too short or too early in time (timestamp near 0 in header.sht which corresponds to 1970). Either try to fill up the data to longer chunks by zeroes or change the start time to a higher value after the year 1980. 
     4> Probably the trace and channel names of the header are not in the schema SxC SZ, SxC SE, SxC SN, SxW SZ, SxN SZ, SxE SZ where x is a number between 1-9. If you have no SNS station architecture try to create copies of existing traces and name them accordingly.[[BR]] 
     5> Another problem can be that the individual traces are too short or too early in time (timestamp near 0 in header.sht which corresponds to 1970). Either try to fill up the data to longer chunks by zeroes or change the start time to a higher value after the year 1980. 
    66 
    7 > NanoseismicSuite / SeisServ is not starting 
    8 >> Delete the seisserv.xml in the userdirectory - nanoseismicsuite - seisserv (Linux: home directory - .nanoseismicsuite) or check the most recent log file under Program Files - NanoseismicSuite - log 
     7== NanoseismicSuite / SeisServ is not starting == 
     8> Delete the seisserv.xml in the userdirectory - nanoseismicsuite - seisserv (Linux: home directory - .nanoseismicsuite) or check the most recent log file under Program Files - NanoseismicSuite - log 
     9 
     10== Error when loading header file == 
     11> Be sure to have no spaces in the directory path where the data is in. If you need a directory with spaces you can manually edit the header and replace the absolute path with a relative like e.g. .\data if the data is in a subfolder data under where the header file is. 
    912 
    1013 
    11 > Error when loading header file 
    12 >> Be sure to have no spaces in the directory path where the data is in. If you need a directory with spaces you can manually edit the header and replace the absolute path with a relative like e.g. .\data if the data is in a subfolder data under where the header file is. 
     14== Data is not available in supported CSS format == 
     15> The software can import MiniSEED, SEG-Y and Lennartz M24 data directly from the Load Data dialog. Converters for other formats into MiniSEED can be found e.g. at IRIS: http://www.iris.edu/pub/programs/converters/ 
    1316 
    1417 
    15 > Data is not available in supported CSS format 
    16 >> The software can import MiniSEED, SEG-Y and Lennartz M24 data directly from the Load Data dialog. Converters for other formats into MiniSEED can be found e.g. at IRIS: http://www.iris.edu/pub/programs/converters/ 
     18== Strange behaviour with protocol entries and hypoprot.txt is not in tmp Folder == 
     19> HypoLine tries at startup to create the tmp Folder in the data directory if it does not already exist. If it exists it tests if it has write permissions there. If one of those two fails, the tmp folder is set to C:\ or the Application Data directory (C:\Users\Username\AppData\Local\VirtualStore). Normally write permissions are available in the data directory and everything is fine but with Windows Vista and 7 if HypoLine runs in the 32 bit compatibility mode the rights management behaves different which forces HypoLine to use one tmp directory for all datasets. This can lead e.g. to protocol entries of old campaigns showing up in new campaigns or other problems related to protocol entries. To prevent this, copy the protfile.txt in e.g. C:\ to the data_directoy\tmp\. 
    1720 
    1821 
    19 > Strange behaviour with protocol entries and hypoprot.txt is not in tmp Folder 
    20 >> HypoLine tries at startup to create the tmp Folder in the data directory if it does not already exist. If it exists it tests if it has write permissions there. If one of those two fails, the tmp folder is set to C:\ or the Application Data directory (C:\Users\Username\AppData\Local\VirtualStore). Normally write permissions are available in the data directory and everything is fine but with Windows Vista and 7 if HypoLine runs in the 32 bit compatibility mode the rights management behaves different which forces HypoLine to use one tmp directory for all datasets. This can lead e.g. to protocol entries of old campaigns showing up in new campaigns or other problems related to protocol entries. To prevent this, copy the protfile.txt in e.g. C:\ to the data_directoy\tmp\. 
    21  
    22  
    23 > Master event moving with ALTGR (CTLR+ALT) + arrow keys does flip screen 
    24 >> The graphics card driver is listening on these keyboard shortcuts, to disable the behaviour, follow this path: [[BR]] 
    25 >> Control Panel → Appearance and Personalization → Display → Screen Resolution → Advanced Settings → Graphics Driver [[BR]] 
    26 >> and disable them. 
     22== Master event moving with ALTGR (CTLR+ALT) + arrow keys does flip screen == 
     23> The graphics card driver is listening on these keyboard shortcuts, to disable the behaviour, follow this path: [[BR]] 
     24> Control Panel → Appearance and Personalization → Display → Screen Resolution → Advanced Settings → Graphics Driver [[BR]] 
     25> and disable them.