<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Software - Geometrics Forum				            </title>
            <link>https://www.geometrics.com/community/geode-software/</link>
            <description>Geometrics Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Tue, 14 Apr 2026 08:34:21 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>What affects Geode trigger cycle times?</title>
                        <link>https://www.geometrics.com/community/geode-software/what-affects-geode-trigger-cycle-times/</link>
                        <pubDate>Mon, 07 Apr 2025 16:12:00 +0000</pubDate>
                        <description><![CDATA[What Affects Geode Trigger Cycle Times?
If you&#039;re trying to optimize your Geode system for faster trigger cycles—especially in high-repeat environments—there are a few key factors to consid...]]></description>
                        <content:encoded><![CDATA[<p class="" data-start="159" data-end="202"><strong data-start="159" data-end="202">What Affects Geode Trigger Cycle Times?</strong></p>
<p class="" data-start="204" data-end="540">If you're trying to optimize your Geode system for faster trigger cycles—especially in high-repeat environments—there are a few key factors to consider. The goal is to ensure that the system completes its entire cycle (trigger → recording → data transfer → re-arming) before the next expected trigger. Here’s what influences that cycle:</p>
<h3 class="" data-start="542" data-end="585">&#x1f9e0; Core Factors That Affect Cycle Times</h3>
<p class="" data-start="587" data-end="625"><strong data-start="587" data-end="625">1. File Size (Sampling Parameters)</strong></p>
Your <strong data-start="633" data-end="652">sample interval</strong> and <strong data-start="657" data-end="674">record length</strong> directly affect the size of each data file.<br />You can view the resulting file size in the <em data-start="765" data-end="789">Acquisition Parameters</em> menu.<br />Larger files take longer to transfer, which delays the re-arm process.<br /><br />
<p class="" data-start="870" data-end="895"><strong data-start="870" data-end="895">2. Data Transfer Rate</strong></p>
The Geode typically transfers data at around <strong data-start="943" data-end="961">450–465 kb/sec</strong>.<br />Reducing file size is the best way to reduce transfer time and speed up the cycle.<br /><br />
<p class="" data-start="1049" data-end="1077"><strong data-start="1049" data-end="1077">3. Calibration Frequency</strong></p>
By default, the system may attempt to <strong data-start="1118" data-end="1145">calibrate every N shots</strong>, which takes additional time.<br />Go to <em data-start="1184" data-end="1207">Options &gt; Calibration</em> and set <strong data-start="1216" data-end="1245">"calibrate every N shots"</strong> to a large number (e.g., 100000) to prevent unnecessary delays.<br /><br />
<p class="" data-start="1311" data-end="1351"><strong data-start="1311" data-end="1351">4. Recording Delay and Record Length</strong></p>
If you're operating in a region with a <strong data-start="1393" data-end="1423">consistently deep seafloor</strong>, you can add a <strong data-start="1439" data-end="1458">recording delay</strong> and reduce <strong data-start="1470" data-end="1487">record length</strong> accordingly.<br />Example: If the water column is always &gt;0.3s, you can apply a delay of 0.2s and reduce record length by the same amount.<br />This trims your file size and speeds up the transfer/re-arm process.<br /><br />
<h3 class="" data-start="1704" data-end="1725">&#x2699;&#xfe0f; Best Practices</h3>
Use the <strong data-start="1737" data-end="1753">Auto-Trigger</strong> function or set trigger sensitivity to the maximum value for testing.<br />Monitor the cycle timing and adjust acquisition parameters to stay within your trigger window.<br />It's often an iterative process to find the ideal configuration for your environment.]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Kolby Pedrie</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/what-affects-geode-trigger-cycle-times/</guid>
                    </item>
				                    <item>
                        <title>What are the system requirements for SCS Seismodule Software?</title>
                        <link>https://www.geometrics.com/community/geode-software/what-are-the-system-requirements-for-scs-seismodule-software/</link>
                        <pubDate>Thu, 31 Aug 2023 17:07:18 +0000</pubDate>
                        <description><![CDATA[The OS software requirements are provided which each release of the software when filling out the ECR/ECO. Those requirements depend on the version released. Over the last 25 years these req...]]></description>
                        <content:encoded><![CDATA[<p>The OS software requirements are provided which each release of the software when filling out the ECR/ECO. Those requirements depend on the version released. Over the last 25 years these requirements have changed. The software only supports Windows. We do not support Linux.</p>

<p>The last version of the <a href="https://www.geometrics.com/wp-content/uploads/2018/10/28519-01_M_Geode-NZ-SmartSeis-ES-3000.pdf">SCS software</a> support all 32-bit and 64-bit of Windows since Windows 7. Windows servers are excluded, since they have not been tested, but should work.</p>

<p>The hardware requirements are more complicated as it depends on the type of seismic survey, number of channels and software product SCS (SGOS, MGOS, ESOS, ...), SAS and options. It also depends how many network cards are needed, sample rate, and record length.</p>

<p>For small systems, SCS will require at a minimum 512MB of free memory. For large systems up to a Maximum of 2GB of free memory. The CPU follow the same pattern. Any CPU since Pentium 90, if supported by the OS, will work for small systems. A bigger survey system and <a href="https://www.geometrics.com/wp-content/uploads/2018/10/Continuous-Recording-Software-Spec-Sheet-v2_0723.pdf">continuous recording software</a> may need i5 or i7 type CPU. An SSD drive may also be needed.</p>

<p>See <a href="https://www.geometrics.com/wp-content/uploads/2020/02/SCS-Software-User-License-Agreement.pdf">SCS software license agreement</a>.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/what-are-the-system-requirements-for-scs-seismodule-software/</guid>
                    </item>
				                    <item>
                        <title>Geode SGOS Timing</title>
                        <link>https://www.geometrics.com/community/geode-software/geode-sgos-timing/</link>
                        <pubDate>Wed, 30 Aug 2023 20:50:38 +0000</pubDate>
                        <description><![CDATA[The time associated with each data point in a SEG-2 data file generated by a Geode is related to the time of the
“trigger” event which was instrumental in the production of the file and its...]]></description>
                        <content:encoded><![CDATA[<p>The time associated with each data point in a SEG-2 data file generated by a Geode is related to the time of the
“trigger” event which was instrumental in the production of the file and its content.</p>

<p><b>The Trigger Master and Trigger Distribution</b></p>

<p>The trigger event occurs at the Geode designated within the Controller software as the Trigger Master.
Although all Geodes are capable of being Trigger Masters, there must be one and only one Trigger Master in
any properly functioning Geode system. The Controller automatically takes care of this requirement when the
designation is made by a user, and when the system is established at the time of Controller start-up based on a
previous designation (or a default setting in the case of a “new survey”). All other Geodes in the system will
have their Trigger Master circuit disabled. A trigger event can be initiated by an external electrical pulse
provided to the trigger input connector of the Trigger Master Geode, or by a command sent via Ethernet from
the Controller to the Trigger Master (usually for test purposes), but only when all conditions are satisfied to
allow data recording. There is also a special trigger initiation situation, called “self-triggering” which will not
be discussed further here.</p>

<p>Upon acceptance of a trigger event, the Trigger Master will distribute the trigger signal to all Geodes in the
system, itself included, via an RS-485 network that resides within the digital interconnect cabling. (Proper
termination of this RS-485 network is automatically taken care of by the Controller.) The trigger signal is
propagated through the cabling and Geodes at the nominal speed of 70% of the speed of light, or approximately
2.1x10^8 m/sec. The maximum distance of successful propagation depends on a number of factors such as the
number of Geodes involved, the noise environment, the quality of the cables, and the acceptable amount of
timing uncertainty for the particular application. Distances approaching or exceeding 1km should be given
careful attention in this regard. In a 3-D Geode system involving LTUs, each LTU, unlike a Geode, will
reconstruct the trigger signal before sending it on, effectively confining the maximum distance issue to each
sub-network separated by LTUs. The penalty is an additional delay of about 100nS for each LTU in the route.</p>

<p><b>The External Trigger Circuit</b></p>

<p>The external trigger input is capacitively coupled, with a 2mS time constant, to the midpoint of a resistive
voltage divider. The voltage difference between the two ends of the divider constitute a voltage "window",
which size is set by the trigger sensitivity parameter and can range from essentially zero at the highest
sensitivity, to about +/- 2.5V at the lowest sensitivity. The Geode will trigger (if enabled) if and when the
coupled signal exceeds the window, in either direction (i.e., positive or negative going). The signal, after the
capacitor, is clamped by diodes to the range between the trigger signal ground and +5VDC.
The trigger detector output is disabled when the system is disarmed, during a parameter change, and during a
shot, up to the trigger hold-off time after the end of the shot. The trigger hold-off time is a parameter set by the
user.</p>

<p>Preceding the coupling capacitor (i.e., essentially the node accessible at pin A of the external connector), there
is a 3.3K-Ohm pull-up resistor to +5VDC (relative to pin B). Also a fast transient suppressor clamps the input
at about +/-14VDC. It is advised that the DC + AC level of any voltage applied to pin A relative to pin B be
kept within the range of +/-7V, giving some margin of safety.</p>

<p>If a DC voltage somewhat less than +5VDC is applied when the connector is first mated, the instrument may
trigger at that moment. But, subsequently, because of the capacitive coupling, it will trigger on the next positive
or negative going pulse that exceeds the window level. If the duration of the applied voltage pulse is less than
the record length + delay time + hold-off time, then the Geode will effectively be ready to trigger on the same
edge of another similar pulse.</p>

<p><b>Sub-sample Synchronization</b></p>

<p>The Geode supports a sub-sample timing synchronization feature used for synchronizing the data acquisition
after a trigger event to the distributed trigger signal, so that subsequent time points will be known to within 1/32
(~1/20 at the fastest two sampling rates) sample interval. It does this by increasing the sample interval at the
trigger time by 0 to 31/32 of a sample interval in increments of 1/32, so that the first sample after the trigger
would represent a time of one sample interval after the trigger event, with a tolerance within 1/32 of a sample
interval. The following samples continue from there at the expected intervals. For example, with a selected
sampling interval of ¼ mS and a recording delay of 0mS, the first sample in the recorded file for each channel
would represent data at 250 to 258uS after the trigger event.</p>

<p>This of course potentially introduces a small discontinuity at the time of the trigger, observable depending on
the nature of the channel waveform(s). (The zero-phase anti-alias filter will smear the discontinuity into the
nearby samples both before and after, consistent with the bandwidth of the filter.) Sub-sample synchronization
can be disabled if it is deemed to be detrimental for the particular application, at the expense of losing the 1/32
interval timing accuracy.</p>

<p><b>Timing Errors</b></p>

<p>The principal errors in Geode timing are of two types: those associated with the trigger mechanism and which
are static over the duration of the record, and those associated with the time base and which change over the
duration of the record. Excluding the trigger propagation delay mentioned above, the trigger timing uncertainty
is about 1uS. The known fixed errors have been lumped together and are reported in the SEG-2 file trace
headers as channel SKEW. (The actual channel skew is zero, since all channels are effectively sampled
simultaneously, but the SKEW value in the header is used as the only place permitting small timing corrections.
Note that the SKEW value for every channel is identical.) If the size of this correction is important to the
application, the SKEW value should be added to the calculated time points when the data is being processed.</p>

<p>The Geode time base has a +/-15ppm stability over temperature (-20C to +70C) and component variations.
Thus time drift relative to absolute time and relative to other Geodes is possible. (However, all channels within
any Geode enclosure use the same time base, so there is no relative drift between channels in the same
enclosure.) Therefore timing uncertainty increases from that existing at the time of the trigger until the time of
the next trigger (or end of record).</p>

<p><b>Special Timing Issues Involved with “Continuous” Recording</b></p>

<p>“Continuous” recording is a method that allows unending 100% time coverage with recorded Geode data. It
produces a series of time-overlapped records created by the use of a negative time delay set equal to the record
length such that each record consists of completed history at the time of the trigger event. This technique
circumvents the problem of data transmission overrunning data acquisition. The principle constraint is that the
cycle time from trigger to trigger must always be less than the chosen record length. Otherwise, gaps rather
than overlap would result. Commonly it is used with GPSderived
triggering in order to provide time-stamping of each trigger event.</p>

<p>Upon consideration of the above, it will become clear that the time-stamp associated with a particular trigger
event will pertain to the data in the following record, not to the data in the record in which the time-stamp is
written. This comes about because the trigger event ends the record.</p>

<p>Because there is data overlap between records, the precise trigger point in the following record at which the
time-stamp applies can be found by comparison of the data values at the end of the former record with those
near the beginning of the subsequent record. The overlapping data will be exactly identical in both records
(since they are read from the same memory location, twice). The earliest data in the subsequent record that
goes beyond the data of the previous record is the data that is one sample interval (assuming sub-sample
synchronization is enabled) past the time-stamp.</p>

<p><i>Note well that this comparison must be made independently for at least one channel of each 8-channel Geode
board set, because the discrete time at which data values are written to the memory buffer, relative to the trigger
event, is a function of each individual board set in the Geode system.</i></p>

<p><b>Correct GPS Time-Stamping</b></p>

<p>There are differences between various GPS models that can affect accurate time stamping. The 1PPS signal
from a GPS has a “timing edge” and return edge, of which only the former is the true whole-second edge.
Some models use a rising edge as the timing edge, some the falling edge, and some have it selectable. Consult
the GPS manual to determine the definition of its timing edge. As indicated earlier, the Geode can be triggered
on either a rising or falling edge. It is important to insure that the Geode is being triggered on the proper edge
in order to avoid timing that may be a fraction of a second off. This is expanded upon below.</p>

<p>Some GPS units provide a very narrow timing pulse, others one that has a nearly 50/50 duty cycle. For the
narrow pulse units, almost certainly it is the leading edge (rising or falling) that is the “timing edge”. This case
can be easily handled by using the Geode Trigger Hold-off feature. If a 10-second cycle time is desired, set the
Trigger Hold-off time to about 9.5 seconds. In this case, there is a very small chance that the very first trigger
could occur on the wrong (trailing) edge, but from then on the leading edge will be used as the triggering edge.</p>

<p>If the GPS provides a 50/50 duty cycle edge, and it is not alterable, then the Geode by itself could as easily start
on the wrong edge as on the correct timing edge, and continue thusly until restarted. For this case, Geometrics
can provide a Trigger Timing Interface Box (TTIB) that will correct the situation. The TTIB can be
programmed to respond only to the correct edge (rising or falling), change the polarity if needed, and gate
through only one of every N 1PPS pulses, where N is programmable. (The TTIB also incorporates an alarm
system that can provide a remote alert if a record is missed.)</p>

<p>Another potential issue comes from the variations between GPS models of the time that the serial time string
(containing the time value of the associated 1PPS) is issued relative to the 1PPS itself. The Geode Controller
attempts to pick the correct serial string based on a calculation involving the known record length, the PC times,
and the trigger notification message from the Geodes. But if the GPS issues the serial string at an unusual time
(and the time has been seen to vary somewhat with a given GPS unit) then it could pick up the incorrect time,
off by 1 second. If rare, it can be subsequently detected and corrected during data processing, but if consistent
it may not be easily detected. Again, the TTIB can accommodate the situation by only gating through to the Controller PC the string belonging to the gated-through 1PPS pulse. The Controller Serial Input Time Window can then safely be widened to 2 seconds (assuming the
cycle time is more than 2 seconds) if need be, to expand the Controller’s search for the string around the calculated trigger time.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/geode-sgos-timing/</guid>
                    </item>
				                    <item>
                        <title>Is there a low cut filter applied, even with all filters set off (to OUT) in the SCS software?</title>
                        <link>https://www.geometrics.com/community/geode-software/is-there-a-low-cut-filter-applied-even-with-all-filters-set-off-to-out-in-the-scs-software/</link>
                        <pubDate>Wed, 30 Aug 2023 20:48:41 +0000</pubDate>
                        <description><![CDATA[Further Elaboration: You might ask this question to try and understand the low frequency response to determine if the Geode amplifiers effectively have a flat response from DC up. Does the G...]]></description>
                        <content:encoded><![CDATA[<p><b>Further Elaboration:</b> You might ask this question to try and understand the low frequency response to determine if the Geode amplifiers effectively have a flat response from DC up. Does the Geode go down to DC for example?</p>

<p><b>Answer:</b> We apply anti-alias filters to the data to prevent out of band noise from being introduced into the data.</p> 

<p>The filters are set with a corner frequency at ¾ of the Nyquist frequency (1/2 the sampling frequency) for almost all of the sampling frequencies.  When we sample at 1.5625 uS, the Nyquist frequency is 32kHz and the filters are set at 20 kHz, because of limitations of our electronics.</p>

<p>There are two single-pole filters: one analog and one digital.  The analog filter is a simple RC filter with 1uF +/-5% and 100kOhm +/- 1%.  We short out the capacitor in the conversion process.  The digital filter is software controlled when the option is registered, so it can be switched in or out in the field.  It is an IIR Butterworth with a -3dB corner at 0.9Hz for 48ksps sampling, and 0.6Hz at all the lower sample rates.</p>

<p>Also, we offer software and  hardware options to modify the low end frequency response of the Geode.</p>

<p>Low-end bandwidth modification:</p>
<ul>1.5 Hz, P/N 28311-37</ul>
<ul>0.6 Hz, P/N 28147-01</ul>
<ul>DC, P/Ns 28147-02, 28311-37per system plus 
</ul>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/is-there-a-low-cut-filter-applied-even-with-all-filters-set-off-to-out-in-the-scs-software/</guid>
                    </item>
				                    <item>
                        <title>GPS Clock Options for the Geode/SCS</title>
                        <link>https://www.geometrics.com/community/geode-software/gps-clock-options-for-the-geode-scs/</link>
                        <pubDate>Wed, 30 Aug 2023 20:43:04 +0000</pubDate>
                        <description><![CDATA[GPS Clocks, used in Continuous Recording systems to provide 1 pps signal to trigger seismograph. Also provides GPZDA serial string to stamp records with UTC for Continuous Recording and Self...]]></description>
                        <content:encoded><![CDATA[<p>GPS Clocks, used in Continuous Recording systems to provide 1 pps signal to trigger seismograph. Also provides GPZDA serial string to stamp records with UTC for Continuous Recording and Self-Triggering systems. Includes cable set to connect clock to PC, seismograph, and 12V DC power.</p>

<p>There are three GPS clock options for the Geode we sell. They are:</p>

<ul>
GS-101B GPS clock from Orca, 1 pps accurate to within 100 ns of the precise time. Includes waterproof antenna with separate electronics module, with display of time and other indicators. Provides time base during loss of satellite lock. Options to provide 1 pps referenced to an IRIG-B generating source and to enclose electronics module in hardened aluminum case (P/N 25374-59). </ul>

<ul>A101 Smart Antenna GPS clock from Hemisphere GPS, 1 pps accurate to within 20 ns of the precise time. Includes waterproof antenna with integrated electronics, with indicator of satellite lock, no display of time. Provides time base during loss of satellite lock. </ul>

<ul>GC200 GPS clock from San Jose GPS, 1 pps accurate to within 1 μs of the precise time. Includes waterproof antenna with integrated electronics, no display of time or other indicators. No time base during loss of satellite lock.
</ul>

<p>The level of precision needed determines which GPS clock is best suited for the job. Typically the GC200 fulfills the needs of 95% of our clients.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/gps-clock-options-for-the-geode-scs/</guid>
                    </item>
				                    <item>
                        <title>Stacking Technical Note</title>
                        <link>https://www.geometrics.com/community/geode-software/stacking-technical-note/</link>
                        <pubDate>Wed, 30 Aug 2023 20:29:03 +0000</pubDate>
                        <description><![CDATA[Stacking is a complicated topic, and warrants its own technical note. Which stacking features are available and how they work depends which modes you are in. There are three main mode “group...]]></description>
                        <content:encoded><![CDATA[<p>Stacking is a complicated topic, and warrants its own technical note. Which stacking features are available and how they work depends which modes you are in. There are three main mode “groups”: SAVE, CORRELATION, AND STACK. Within those are sub modes whose names indicate their function.</p>
<p><b>Save</b></p>

<ul>Autosave</ul>
<ul>Manual Save</ul>

<p><b>Correlation</b></p>

<ul>No correlation</ul>
<ul>Standard correlation

<ul>Stack before Correlation</ul>
<ul>Stack after Correlation</ul>

<ul>Random Source Correlation</ul>

<p><b>Stack</b></p>

<ul>Autostack</ul>
<ul>Replace</ul>

<p>There is a complicated interplay between the above modes and between these modes and the stack  options:</p>

<ul>Stack polarity</ul>
<ul>Display Intermediate Stacks</ul>
<ul>Unstack Delay</ul>

<p>We will examine each possible combination in rough order of popularity</p>

<h4>Modes:  Manual save , No correlation, Autostack</h4>
<img width="400" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SGOS Stacking/Stacking 1.png">
<br></br>

<p>This is the most common configuration used in <b>refraction and downhole</b> surveys.</p>

<ul>Each shot is automatically stacked</ul>
<ul>Each stacked record is displayed as the stack count increments</ul>
<ul>The stack count continues to increment with each shot until you clear the data, even if you save the data sometime in the process.</ul>


<p>Stack Polarity can be changed at any time. This is most often used in shear wave surveys where reverse-polarity stacking is required.</p>
 
<p>Unstack Delay gives you the option to unstack the most recent stack; for example, setting the stack count from 4 back to 3.  The data will be held in a temporary buffer for n seconds, during which time you can choose whether to stack or not.  If you do nothing, the data will be automatically stacked after n seconds, and unstacking will be no longer be an option for that stack. If Unstack Delay is set to zero, this feature is disabled.</p>

<h4>Modes: Auto Save, No correlation, Autostack</h4>
<img width="400" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SGOS Stacking/Stacking 2.png">
<br></br>

<p>This is the most common configuration used in <b>impulsive reflection</b> surveys.</p>

<ul>Each shot is automatically stacked until the Stack ulmit  is reached.</ul>
<ul>When the Stack ulmit is reached, the data are saved automatically.</ul>
<ul>Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data.</ul>
<ul>Stack Polarity is generally left set to Positive.</ul>
<ul>Displaying intermediate stacks is optional.  Disabulng this option results in faster production, since the data do not need to be sent over the network with every stack.</ul>


<h4>Modes: Auto Save, Standard Correlation, Stack Before Correlation</h4>
<img width="400" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SGOS Stacking/Stacking 3.png">
<br></br>
<p>This is the most common configuration used in <b>swept-source reflection</b> surveys.</p>

<ul>Each shot is automatically stacked until the Stack ulmit is reached.</ul>
<ul>When the Stack ulmit is reached, the data are saved automatically.</ul>
<ul>Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data.</ul>
<ul>Data are stacked in raw, uncorrelated form in the Geodes, and are not sent to the PC until the Stack ulmit is reached.</ul>
<ul>When the Stack ulmit is reached, the stacked raw record is correlated in the Geode (with the most recent pilot), sent to the PC, and saved.</ul>

<h4>Modes:  Auto Save, Standard Correlation, Stack After Correlation</h4>
<img width="400" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SGOS Stacking/Stacking 4.png">
<br></br>
<p>This is the most common configuration used in <b>Random Source (mini-Sosie) reflection</b> surveys.</p>

<ul>Each shot is automatically stacked until the Stack ulmit is reached.</ul>
<ul>When the Stack ulmit is reached, the data are saved automatically.</ul>
<ul>Data are automatically cleared and the stack count is reset to one the next time the seismograph triggers after saving the data.</ul>
<ul>Each individual record is correlated with its own pilot and stacked in correlated form in the Geodes.</ul>
<ul>Displaying intermediate, correlated stacks is optional.</ul>
<ul>When the Stack ulmit is reached, the stacked, correlated record is sent to the PC and saved.</ul>


<h4>Modes: Auto Save, Replace</h4>
<img width="400" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SGOS Stacking/Stacking 5.png">
<br></br>

<p>This is the most common configuration used in <b>Continuous Recording</b> surveys.</p>

<ul>Each stack is replaced by the previous. If Auto Save is not enabled, the previous stack is lost.</ul>
<ul>If Auto Save is on the Stack ulmit is hard-coded to 1.</ul>
<ul>Each shot is displayed.</ul>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/stacking-technical-note/</guid>
                    </item>
				                    <item>
                        <title>Understanding Acquisition Filters in Seismographs - Their Use and how to Filter</title>
                        <link>https://www.geometrics.com/community/geode-software/understanding-acquisition-filters-their-use-and-how-to-filter/</link>
                        <pubDate>Wed, 30 Aug 2023 20:27:57 +0000</pubDate>
                        <description><![CDATA[Low Cut: , 10, 15, 25, 35, 50, 70, 100, 140, 200, 250, 280, 400
Notch: 50, 60, 150, 180
High Cut: 32, 64,125, 250, 500 or 1000 Hz

The first recommendation for cases when you are having ...]]></description>
                        <content:encoded><![CDATA[<p>Low Cut: , 10, 15, 25, 35, 50, 70, 100, 140, 200, 250, 280, 400</p>
<p>Notch: 50, 60, 150, 180</p>
<p>High Cut: 32, 64,125, 250, 500 or 1000 Hz</p>

<p>The first recommendation for cases when you are having trouble getting sufficient signal to noise would be to increase your signal via stacking the data with multiple source events or get a more powerful seismic source. This will usually produce better results than the application of filters.</p>

<p>Another approach would be acquire data when the noise sources are less present. That may mean collecting data at night when the area is closed or the traffic is less.  Early morning can be better for areas where the wind tends to increase during the day.</p>

<p>The selection of filters is very site dependent and can depend on a variety of factors as well as the type of survey being performed.</p>

<p>1) Typically the Notch filters are to remove noise due to electrical power lines (50 or 60 Hz and their harmonic frequencies depending on the country you are in).</p>

<p>2) Low cut filters are generally used for noise due to wind and moving vehicles, but care must be taken not to remove too much bandwidth from generated seismic signal.  Often the noise sources have the same frequencies as the seismic data you are interested in and can’t be effectively removed using frequency filtering.</p>

<p>3) High cut filters can be used to remove noise from high frequency vibratory signals such as compressors or airplanes.</p>

<p>In general it is best to record the data without any frequency filters and filter in post processing or only on the displayed data in our software. It will be a matter of experimentation to determine the best filters at your site.</p>

<p>Modern 24-bit seismographs (Geode, Stratavisor, ES-3000, etc) have a much wider range of signal amplitudes that they can record accurately. This means that they can still accurately record smaller seismic signals even in the presence of larger noise signals. Therefore there is a reduced need for analog filters that are applied prior to digitization of the signals.</p>

<p>Digital filters are more flexible and can be more specifically applied to the noise that is recorded rather than the “Broader Brush” of analog filters. Digital filters also have the benefit of being able to go back to the original data if the wrong filter is applied, which is not the case with Analog filters. The general approach in the seismic industry is now to record everything – including the noise – and the filter out what you don’t want later.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/understanding-acquisition-filters-their-use-and-how-to-filter/</guid>
                    </item>
				                    <item>
                        <title>Channel remapping in SGOS</title>
                        <link>https://www.geometrics.com/community/geode-software/channel-remapping-in-sgos/</link>
                        <pubDate>Wed, 30 Aug 2023 20:24:07 +0000</pubDate>
                        <description><![CDATA[Channel Remapping
Channel remapping allows you to change:

the order of channels on each analog spread
cable that connects to the Geode
reorder the Geode boxes.





You would use...]]></description>
                        <content:encoded><![CDATA[<h4>Channel Remapping</h4>
<p>Channel remapping allows you to change:
<ul>
the order of channels on each analog spread
cable that connects to the Geode</ul>
<ul>reorder the Geode boxes.</ul>

</p>

<img width="400" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping3.jpg">

<p>You would use this option if your cables were wired
opposite to the default order normally used in
Geometrics wiring, if you wished to turn your line
around to have the low channels at the opposite end, or if your cables had a wiring error. Channel
remapping is also often necessary when using more that a single network cable.</p>

<h4>Default cable wiring of Geometrics seismographs</h4>
<p>Default order is defined as the natural electrical order in which channels are oriented when the
system first powers up before remapping. Refer to Section 3 under Connector Wiring that
discusses standard wiring configurations. You may have requested a custom wiring configuration
from Geometrics. If you are confused about your wiring, contact the factory and refer to the serial
number and job number.</p>
<img width="400" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping4.jpg">
<p>Geode cables are typically wired in a ‘high-side
configuration’, meaning that the Geode connects closest
to the highest numbered channel on the analog cable. The
149
figure above shows this configuration for a single box system, with 24 channels.</p>

<h4>Multiple Geodes</h4>
<p>The following diagram shows a default single digital line (one network card) system with 3
Geodes. Note that Geode one is always closest to the controller in a default configuration.</p>
<img width="800" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping5.jpg">

<h4>Multiple Network Lines</h4>
<p>The next diagram below shows a default configuration with two digital lines (two network cards)
with the controller positioned in the middle. Line 1 is on the left and line 2 is on the right. One
might use two lines to increase data throughput to reduce time between shots. Like the
configuration above, the Geodes are numbered starting closest to the controller. The seismic
controller software labels all of the channels contiguously even though they are on two separate
digital lines. However, if the lines are collinear, the first line will have the channels ordered
backwards. This can be easily rectified with the remapping feature.</p>
<img width="800" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping6.jpg">
<p>There are two ways of remapping channels: automatic mode and manual mode. Automatic mode
settings are listed on the top of the remapping dialog box, and manual mode on the bottom.</p>

<h4>Automatic Channel Remapping</h4>
<p>Automatic channel remapping allows you to reverse
either the order of the Geodes on the line, or reverse the order of the channels on the spread cable.</p>
<img width="400" align="float-left" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping7a.jpg">
<img width="400" align="float-left" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping7b.jpg">
<p>The above diagram shows the result after both channels and Geodes have been reversed,
renumbering the line so that low channels start on the left hand side and increase towards the
right. In the dialog box, the automatic remapping boxes referencing line 2 remain unchecked,
since the default orientation on line two was correct.</p>

<h4>Manual Channel Remapping</h4>
<p>Channels can be remapped on an
individual basis using the Manual Map
Mode. Select the appropriate check box,
and enter the order in which you would
like the channels that differs from the
default order. You can specify individual
channels separated by a comma (1, 3, 4, 6
etc) or a range of channels (1-13, 24-14
etc).</p>
<img width="400" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geode Timing/Geode Channel Remapping8.jpg">
<p>For example, if you wanted the channels
ordered backwards on a 24-channel
system, you would enter 24-1. If you
wished to reverse the order of channels 1-
12 in a 24 channel system, you would type
12-1, 13-24. Other examples are shown opposite, and are available by pressing the See Examples
button on the remapping menu.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/channel-remapping-in-sgos/</guid>
                    </item>
				                    <item>
                        <title>Understanding the SGOS Geometry Window GUI</title>
                        <link>https://www.geometrics.com/community/geode-software/understanding-the-sgos-geometry-window-gui/</link>
                        <pubDate>Wed, 30 Aug 2023 20:23:08 +0000</pubDate>
                        <description><![CDATA[The Geometry GUI provides a graphical representation of your survey, along with a wide range
of control capability. It is particularly useful when conducting reflection surveys, but can be...]]></description>
                        <content:encoded><![CDATA[<p>The Geometry GUI provides a graphical representation of your survey, along with a wide range
of control capability. It is particularly useful when conducting reflection surveys, but can be
useful in a wide range of applications. It summarizes, in one simple view, the physical positions
and other attributes of the hardware on the ground, and allows graphical control of these.</p>
<p>Below is a typical display of a 96-channel, four-Geode layout. We will first describe the display
itself, and follow with a description of its control capabilities.</p>
<img width="600" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geometry GUI/Geometry1.jpg">
<p><i>Example Geometry GUI</i></p>
<br></br>
<img width="600" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geometry GUI/Geometry2.JPG">
<img width="600" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geometry GUI/Geometry3.JPG">
<img width="600" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/Geometry GUI/Geometry4.JPG">]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/understanding-the-sgos-geometry-window-gui/</guid>
                    </item>
				                    <item>
                        <title>SGOS Calibration</title>
                        <link>https://www.geometrics.com/community/geode-software/sgos-calibration/</link>
                        <pubDate>Wed, 30 Aug 2023 20:18:30 +0000</pubDate>
                        <description><![CDATA[Standard Procedure on Registering SCS Software

Here&#039;s our standard procedure on registering the SCS (Seismic Controller Software):

The latest version of the SCS is 11.1.69, which is us...]]></description>
                        <content:encoded><![CDATA[<h4>Standard Procedure on Registering SCS Software</h4>

<p>Here's our standard procedure on registering the SCS (Seismic Controller Software):</p>

<p>The latest version of the SCS is <a href="https://www.geometrics.com/wp-content/uploads/2018/10/SCS_Installation.zip">11.1.69</a>, which is used for Windows Operating Systems up to and including W-10 64 bit computers.</p>

<p>Within the zip file you will find instructions as well as the installation file.</p>

<img width="400" align="middle" src="https://www.geometrics.com/wp-content/themes/geometrics/images/FAQs/SCS Registration Procedure.jpg">

<p><b>Note: Installing the WinPcap is mandatory!</b></p>

<p>After installing, you will need to register. In order for us to issue the correct SCS registration we will need additional information. The preferred method is:</p>

<p>1. From the “Registration Window” select “Send Email or Save File to Disk”.</p>
<p>2. Fill out the report, to include serial number of seismograph. (type 0000 in sales No. field if not known)</p>
<p>3. Save the file to your computer.</p>
<p>4. Send an email with the file attached or embedded to: rrivera@geometrics.com and/or support@geometrics.com.</p>

<p>We will then remit with a 40 character alphanumeric string that you can paste into the same “Registration Window.”</p>

<p>Please understand that the SCS can be installed onto as many computers as you wish, yet each installation will generate its own unique user code and therefore need to be registered.</p>]]></content:encoded>
						                            <category domain="https://www.geometrics.com/community/geode-software/">Software</category>                        <dc:creator>Gretchen Schmauder</dc:creator>
                        <guid isPermaLink="true">https://www.geometrics.com/community/geode-software/sgos-calibration/</guid>
                    </item>
							        </channel>
        </rss>
		