GE LOGIQ 7 Basic User Manual page 259

Hide thumbs Also See for LOGIQ 7:

Table of Contents

Table 5-8: 3D Acquisition Description and Instructions for Use

3D Parameter

Acquisition Mode

Selections: Sensorless Parallel, Sensorless Sweep, With Sensor

Sensorless Parallel. In this mode the probe must be moved during 3D data

acquisition without angling it. You should scan the object you want to render in 2-4

seconds. The speed at which you scan should be constant. No sensor is mounted on

• Since the time for post-processing depends on the acquired number of frames, it is

Sensorless Sweep. In this mode the probe must be moved to a position where you

can clearly see a middle cut of the object you want to scan and render. Tilt the probe

to about 30 degrees until the object you want to scan disappears. Start the acquisition

and tilt the probe over a distance of around 60 degrees until the object disappears

again. The entire scan time should be around 2-4 seconds. During the sweep, the

probe may not be moved parallel, just tilted. No sensor is mounted on the probe.

Before starting an acquisition, take care that the transmitter is positioned correctly

during data acquisition and that the transmitter cannot move.

Selections: Front to Back, Side to Side

Front to Back. After having scanned in this mode, the rendered dataset is shown in a

frontal view. For acquiring a fetal face in sagittal cuts, use this mode.

Side to Side. After having scanned in this mode, the rendered dataset is shown from

a side view. For acquiring a fetal face in coronal cuts, use this mode.

Starts the rendering process.

Scan Distance

Adjusts the distance covered during the scan. Depending on the real width of a scan

acquired during a sensorless 3D acquisition, the volume of interest's width can be

enlarged or reduced. You can adapt the form of a fetal face if the baby's head looks

oval instead of round. The assumed default width of a parallel scan is 6 cm; of a fan

scan 60 degrees.

LOGIQ 7 Online Help

Direction 2392536-100 Rev. 1

recommended that you check the frame rate. Low frame rates result in fewer

acquired frames for the 3D dataset which results in intensive post-processing

(interpolation). Therefore, low frame rate = long post-processing.