Notifications
Clear all
Search result for: id10=WA 0859 3970 0884 [[HATIGA]] Order Atap Canopy Alderon Single Layer Murah Wonosari Klaten
Page 1 / 3
Next
A velocity inversion refers to the case when seismic velocity decreases, rather than increases, with depth. When this happens, energy refracts away from the normal:
This means that no information from the refracting interface returns to the surface, hence no information is gained about that interface, even its very existence.
This is demonstrated by the animation below. There are three distinct velocity Layers, but Layer 2 is slower in velocity than Layer 1. The result is a travel time curve that indicates the presence two Layers -- Layers 1 and 3. Layer 2 is not sampled, so there is no evidence of its presence in the record. However, the presence of Layer 2 does impact the travel time plot by moving the crossover distance out farther than it would be otherwise. The result is that not only is Layer 2 not detected, but the depth to Layer 3 is incorrect -- it is calculated to be deeper that it is.
The crossover distance is the distance from the source at which the critically-refracted energy from the next deepest Layer overtakes the critically-refracted energy from the previous Layer (in the two-layer case, the energy traveling through Layer 1 is direct, not refracted energy, but the idea is the same). This is illustrated by the following animation:
The direct energy (red) is the first-arrival energy at the first six geophones. However, by the seventh geophone, the direct energy is overtaken by the critically-refracted energy (green). The reciprocal of the slope of each segment is equal to the apparent velocity of the material. If there were a third, even faster Layer, a third slope and second crossover distance would eventually appear on the travel time graph. The crossover distance, along with the velocities indicated by the slopes of the segments, are used to determine the refractor depth.
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 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.
Default cable wiring of Geometrics seismographs
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.
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.
Multiple Geodes
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.
Multiple Network Lines
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.
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.
Automatic Channel Remapping
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.
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.
Manual Channel Remapping
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).
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.
Hello everyone, my name is Devan, and I would like to open a discussion about finding a lost MagArrow.
To give you some background, I lost my MagArrow II while it was mounted below the DJI M400 during a flight mission in a highly dense forest. We have the drone flight log, which indicates that it was stuck in a tree within a 50 m radius of the last known location. We have searched the whole area, but due to a highly dense forest and steep terrain, it was very difficult to find the MagArrow II and the drone on foot.
For more than a month, I presume it was still perched within the tree Canopy. And now we have bought a new MagArrow II to continue our survey. In this case, I desperately want to find and retrieve the lost MagArrow using the new device.
I have an idea that if I conduct a 5 m spacing grid in both East-West and North-South directions within a 100-meter radius of the last known location, we could eventually narrow down our perimeter by finding an anomaly that indicates the lost device. Therefore, I have a few questions:1. How magnetic is the drone and the MagArrow II?2. Is it feasible to find the old MagArrow with the new MagArrow with the stated method? Alternatively, do you have any effective suggestions for a different approach?
I appreciate any insights you can provide. Thank you!
I have attached the instructions that are sent with a new Order acknowledgment. (Installation and Transfer)
The license is assigned to a specific Registration ID once fully purchased. This ID can be assigned to a person (we like to know for our own records) if possible but not required and can be transferred to other PC’s as needed. The ID works like a softkey dongle. The software can be active on only one machine at a time.
I attached a simplified “Steps with windows_SI Transfer procedure that shows how the software can be moved. The PC must connected to the internet to affect the first part of the transfer (which removes the ID from the PC, making available for the next). Then to place the Reg ID on the next computer is just following the original registration process.
Do not lose the ID. Make sure that the ID has been removed before a disc is reimaged or an employee leaves with the PC. If for some reason the Reg ID has to be reset, (computer dies before the ID can be removed) I will require a statement and an end user then for my records.
I am available to discuss if needed at the number below 0700-1500 PST.
Best,
RandL P RiveraCustomer Service Repair Supervisor+1 (408) 428-4254 (direct)+1 (408) 954-0522 (office)support@geometrics.com
Attachment : SeisImager_LicenseTransfer_Instructions_v1.2.pdf
Attachment : Steps with windows_SI Transfer.pdf
Attachment : SeisImager_Installation_Instructions_v7.6.pdf
Color representationRed: data collected by a survey magnetometer, such as a MagArrowGreen: survey data we are interested inBlue: base-station data
Magnetic field is a function of location (r) and time (t): B(r,t)In general, we are only interested in magnetic field as a function of location: B(r).
Ideally, we set up one magnetometer at each location of interest and measure the magnetic field at different locations at the same time. This method removes the time dependence.However, the method requires many magnetometers. The common practice is to move one magnetometer around. In this case, B(r,t) is collected since it takes time to move the magnetometer.
To remove the time dependence, a base-station is required. Assume the base-station reading at a fixed location R1 is B1(R1,t) = c1 + B1(t), where c1 is a constant, depending on R1. We hope to achieve the base-station correction B(r,t) - B1(R1,t) = B(r) – c1.For a Single base-station location, c1 can be ignored since it is a constant offset applied to the whole survey area. In another word, B(r) and B(r) – c1 generate the same survey color map.
For large scale surveys, it is impossible to have a Single base-station location, since it is not economical and magnetic field time dependence is also regional.Now we obtain base-station data sets at different locations: B1(R1,t), B2(R2,t), B3(R3,t)…
When the base-station correction is applied, Bi(r,t) - Bi(Ri,t) = Bi(r) – ci. In general, ci are different. Therefore, Bi(r,t) - Bi(Ri,t) can NOT be combined directly into a Single data base unless constant offsets are applied to achieve Bi(r).
A typical combined 5-day survey without applying offsets is shown below.
These constant offsets are hard to measure, unless multi base-stations are set up. However, they can be calculated based on the overlapping areas between two data sets since the readings in the overlapping areas must be the same, assuming the same AGL (above ground level). With this method, the new combined data is shown below.
Geometrics offers an auto survey combination program for MagArrow and MagEx customers.
Attachment : Survey_Data_Stitch_Auto_V3.zip
You can transfer your SeisImager license from one computer to another using the following guide.
SeisImager has a function to erase velocity model where ray path did not propagate.
It is not automatic.
Select "Velocity model", ""Define bottom Layer", "Manually".
Then click the mouse from left to right to define a line to truncate velocity model as shown below.
Final Result:
Every second, the NMEA strings, delimited by Single quotation marks, are included as separate columns. The strings also contains commas. Therefore, there will be more columns if you use comma as the only delimiter.
The correct import setting should be comma-separated, with Single quotation marks as string delimiters. All of those "extra" columns will be revealed as the original RMC and GGA NMEA strings.
Dead-Zones
The MagArrow is a dual sensor magnetometer powered by MFAM sensors, but it is configured for use so it only has a Single data output. The reason Geometrics has done this is so we could ensure the MagArrow encounters no "dead-zones". A dead-zone occurs when the orientation of a magnetometer results in the magnetometer producing poor or no measurements. The dead-zone angle depends on the location of survey.
Since we have the two MagArrow MFAM sensors in orthogonal orientations, the MagArrow Magnetometer has operability worldwide without affecting survey orientation, making it much easier to use for the customer.
Heading Errors
Heading errors are a type of noise magnetometers can experience. They come from three sources:
Sensor
Console
Operator
Magnetic materials in the sensor itself are the primary cause of heading errors. The physics of Cesium and Potassium magnetometers can contribute small amounts to the total heading error. Magnetic contamination near the sensors, operating electronics, or operator can all contribute to heading error.
Heading errors look like herringbone patterns in survey images. Alternate lines can also be corrugated.
Dead-Zones vs Heading Errors
while these two sources of error in magnetic data are different, there is overlap between them when operating a magnetometer like the MagArrow.
Heading errors can be fixed relatively easily in software, where dead zones can be much harder to manage. If a line is completely ruined because of a dead zone then they will need to re-fly the line/mission which is time consuming. Even with advanced users, these sorts of mishaps can happen.
Additionally, the closer a mag sensor operates to a dead-zone, the larger a heading error will be measured. With compensation software and a pre-survey heading error flight, heading error can be reduced dramatically to around 1 nT for the MagArrow.
Click to view the difference between Raw and Processed MagArrow Data
The MagArrow is only outputting a Single value as a means to create a “no-dead-zone” system. Obviously each sensor has a dead zone themselves, but with the sensors orientated orthogonally at least one sensor at all times will have a magnetic measurement. By combining the measurements from both sensors it is possible to generate a constant magnetic field measurement independent of orientation and location in the world. If the data from each MFAM sensor in the MagArrow was individually reported there would be gaps in the mag fields observed by either sensor as you fly, rotate, and swing.
Raw Data
MagArrow data is imported into Survey Manager in the form of .MAGDATA files, downloaded from the MagArrow. The .MAGDATA file contains measurements from different sensors inside the MagArrow: 1000Hz magnetometer readings; accelerometer, gyro, compass, temperature readings; and GPS info.
MFAM assigns a fiducial number, or “FID” to each magnetometer reading, in a cycle from 1 to 1000 that repeats every second. In the instrument, the magnetometer readings and the GPS sentence data are synchronized so that the “FID-1” magnetometer record is matched with the GPS location and timing information.
Exports to CSV and Geosoft file formats
1000Hz un-filtered export
The 1000Hz export provides the original raw magnetometer data plus some simple interpolations:
• Magnetometer reading: The raw magnetic field values are exported without application of a filter. [While these raw measurements are the output of a filter inside the MFAM sensor: a 9-pole Butterworth low pass filter with a -3dB point at 400Hz, that filter is considered part of the sensor for this description.]
• Auxiliary sensors: Gyro, accelerometer, and temperature are acquired once per every 5 magnetometer readings, and are reported only when acquired. Compass readings are acquired one per every 10 magnetometer readings and are reported only when acquired.
• GPS NMEA sentence: Reported with the associated FID-1 mag record. A few individual fields from the GPS are also broken out from the GPS sentence and reported separately, without interpolation.
• Interpolated GPS fields: Time, date, latitude, longitude, and track (course over ground) are linearly interpolated between GPS readings.
Decimated exports
Each of the exports at frequencies from 10 Hz to 100 Hz is a decimation – data are filtered by a low-pass filter and then down-sampled to the target sample rate. Each low-pass filter (a different one for each decimation) is a symmetric finite impulse response (or FIR) filter, with the following design goals:
• -3dB attenuation at 0.75 * Nyquist frequency (e.g., the -3dB point for the 10Hz decimation is 3.75Hz)
• Significant attenuation of 50Hz and 60Hz signals.
• Reasonably flat response in the pass band.
Linear phase (or zero phase, or constant group delay) filters.
These filters are not Kalman filters. The filters are applied to fields in the decimations as follows:
• Magnetometer readings: Magnetometer readings are decimated: the FIR is applied, then the data are down-sampled to the target rate.
• Aux sensors: Aux sensors are first up-sampled to 1000Hz by linear interpolation of values between individual readings (which occur once every 5 mag readings for gyro, accelerometer, and temperature, and once every 10 mag readings for compass). Then these 1000Hz values are decimated in the same process as the magnetometer readings.
• Latitude and longitude are first up-sampled to 1000Hz by linear interpolation of values between successive GPS data (once per second), then these 1000 Hz values are decimated in the same process as the magnetometer readings.
• Time, date, and track are linearly interpolated as in the raw, unfiltered 1000Hz export.
Merging filtered and unfiltered data.
Some of the values in an individual line of data are filtered: mag readings, aux sensors, etc. Other measurements are not filtered: time and date, GPS sentences, record counters, and the simple interpolated fields. These two sets of values – filtered and unfiltered, must be reported in individual lines that contain values of both types. The question “How should the two sets of values be matched?” is addressed as follows:
A decimation filter has a center. For example, a Single filter result that weighs 499 individual measurements running from record number 752 to record number 1250 (in DSP terms, it is the result of the convolution of 499 input values with 499 filter weights), is centered on record number 1001. The result is the “filtered value of record 1001”. In a Single line along with this value should be the other filtered results centered on record number 1001 plus the unfiltered raw and interpolated values that were recorded as part of the original, raw record 1001.
The down-sampling part of decimation involves keeping some results and discarding others; down-sampling from 1000Hz to 100Hz includes discarding 9 out of 10 results. During exports, Survey Manager keeps the “FID 1” record, because it includes the original GPS information, then discards the next 9 records (if it’s a 100Hz decimation), and then repeats the pattern, each time starting with FID 1.
If you have questions about the MagArrow decimations, please contact your Geometrics account manager.
A common question many have with magnetic surveys is "How wide of a survey swath does a Single magnetometer sensor cover on a Single pass?" The answer is it depends on what is being searched for.
Magnetometers are passive instruments, meaning they don’t actively send out signals or have a limited swath or depth of exploration.
When planning a magnetic survey the grid (line spacing and waypoint spacing) should be designed using the best possible model of the target. There are some general rules of thumb that can be used to determine typical detection ranges for common iron objects. For example, a 10lb sledgehammer has been lost and needs to be found, and assuming this is 10lbs of pure iron, it would be expected to see a 1nT anomaly when the magnetometer sensor passes 6 meters over the top of the tool. Knowing this, survey line spacings should not be any narrower than 6 meters. With a line spacing of 3 meters, the chances of getting a clear anomaly goes up 8 fold as the 10lb iron sledgehammer would be at a minimum a 8nT anomaly vs a 1nT anomaly.
In a geological sense, let's say we have a mafic dike intrusion that we believe is running E-W and it extends at least 25 meters in the near-surface in a somewhat linear fashion. It's difficult to model the amount of iron in a geological structure like this, so the survey should be designed to cross the dike perpendicularly every 5 meters or so, making sure to cross over the dike several times. Each pass over the dike may exhibit an anomaly of similar amplitude, and the feature will show up as a clear linear feature in the final processed map.
For general mapping of geology, you have a lot of options. Most commonly mineral exploration surveys are done over very large areas, so the line spacing is wider to save time as the lower resolution model that results still accomplishes the task of finding large mineral deposits. If more detail is required, then a more fine-grained survey can be done later. 20m-50m line spacing is typical for mineral exploration surveys.
Design a survey grid to completely encompass the area of interest (i.e. make sure you get some data outside of the areas of interest, in case an interesting anomaly lies right along the edge). The founder of Geometrics the late Sheldon Breiner called this the Law of Search, as he often found his targets of interest along the edges of his archaeological magnetic surveys.
It is important to make sure the operator of the magnetometer is magnetically clean before surveying with the magnetometer. This means no steel toe boots, glasses or hats with metal fittings, cellphone, belt buckle, etc.
Magnetometer data acquisition is fairly simple, but data interpretation can be complex.
You may need a base-station too. Please refer to the Base-Station information.
If you're exporting data from G-864, MagArrow, or MagEx, using any of the export tools - Quick Conversion, Command-line conversion, or export from a project and survey in Survey Manager - and you don't get any data, or you think the export is missing some data, follow these steps:
Verify that you have records to export:
In survey manager, verify that the survey has data in it: there's a "Measurements" field in the survey details. For MagArrow, if you're using Quick Conversion or the command line program, you will need to create a project and survey in Survey Manager and import the .magdata file into it.
If you don't have any data records, then verify that you've opened the correct file.
If you have records, but they just don't seem to be exporting, then choose to export invalid records and records without locations
The export functions in Survey Manager allow you to choose this option with the "Filter" choices:
Look in the exported file for records without locations (no GPS) and with invalid records; they are not included in the default exports.
For MagArrow, export with 1000 samples/second. If you are troubleshooting an export at a decimated rate (e.g. 20 samples/second) then note that a Single invalid record in the 1000 samples/second original data may invalidate about 1/2 second of data; in a 20 samples/second MagArrow decimation, a Single 1000 samples/second invalid record will invalidate about 10 decimated results.
Overview
The MagEx instrument and the MagNav app both display information about the state of the instrument's battery. Battery state and reporting exist in bands according to percentage of remaining battery capacity:
30% or higher:The instrument has good remaining capacity.The LED on the instrument's power switch glows a solid green.MagNav displays the battery percentage or voltage in black text on a white background.
Between 20% and 30%:The instrument has capacity to survey for additional time, but if you will be surveying a significant amount more, start thinking about changing the battery.The LED on the power switch is blue.MagNav displays the battery percentage with a blue background.
Between 5% and 20%:You can continue to survey, but the battery is running low and you should consider changing the battery soon.The LED on the power switch is red.MagNav displays the battery percentage with a red background, and periodically notifies you that the battery is running low.
Below 5%:The battery is running low, and the instrument may turn off at any time in Order to preserve battery health. You should change the battery as soon as possible.
Temperature-related effects:Battery performance also changes as the temperature of the battery changes; as the temperature of a battery falls, the voltage it supplies also decreases, and the total energysupplied by the battery decreases. This means that in cold weather a battery will not last as long as in hot weather.
The battery percentages reported in the instrument are adjusted for the effect of temperature; at a given battery voltage a cold battery will display a higher percentage than a warm battery will report.
The effects of colder temperatures are not normally permanent; as a battery warms up, its output voltage and energy return to higher levels.
Notes about the calculation:The MagEx instrument includes 2 batteries, and each battery includes 3 separate cells. Battery percentages are calculated from only one battery in the instrument - either the Single battery if only one is connected, or from the better battery if two batteries are connected.
Reported battery percentage is an estimate, based on measurements of the behavior of healthy batteries in instruments in the field and in the lab. Battery performance may change as a battery ages and as the temperature changes.
The best practice for batteries is to use 2 healthy, fully charged batteries, and replace them both when the percentage falls below 20%.
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.
The Trigger Master and Trigger Distribution
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.
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.
The External Trigger Circuit
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.
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.
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.
Sub-sample Synchronization
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.
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.
Timing Errors
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.
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).
Special Timing Issues Involved with “Continuous” Recording
“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.
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.
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.
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.
Correct GPS Time-Stamping
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.
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.
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.)
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.
Our cesium-vapor magnetometers do not require periodic calibration in Order to maintain the accuracy as described in our published specification when the instrument is operated within specified environmental ranges. Geometrics cesium-vapor magnetometers are manufactured and tested based on the discoveries and the basic designs of Carian Associates (U.S. Patent 3,071,721). This method of total magnetic field measurement relies upon the measurement of the optical absorption of a particular cesium spectral frequency by the cesium vapor enclosed in a small glass cell. This method is similar to those used in the measurement of atomic emission and absorption frequencies using spectroscopic reference cells. The technique thus relies on well-known fundamental quantum mechanical constants for accurate and precise measurement of the magnetic field. As a result, no adjustments to the sensor are needed in Order to correct or maintain its accuracy and Geometrics sensor and sensor driver electronics are designed to either work correctly or to not work at all and to report both the strength of the magnetic field as well as the strength of the electrical signal produced by the working sensor. In this way, the signal strength measurement provides a direct indication of the operational state of the magnetometer while it is running and serves to alert the operator if the magnetometer encounters environmental conditions that are outside of its operating range.
Occasional maintenance of the instrument at Geometrics facility should be performed when the instrument's internal diagnostics indicate substandard performance as described in the operator's manual.
Please contact Geometrics Support for technical advice and additional information pertaining to your specific model.
Page 1 / 3
Next