Actions

7T general info & troubleshooting: Difference between revisions

From SpinozaWiki

Misc (talk | contribs)
 
(104 intermediate revisions by 12 users not shown)
Line 1: Line 1:
Overview page for 7T related information
Overview page for 7T Achieva related information


= Table operation =
= Table operation =


* '''Important: move table to fully outer position before resetting or undocking'''
* When pulling the table out, stop when 'table out' LED turns on. Don't pull further than backside of bed. When undocking, the bed will be pushed back the remaining centimeter.
* Move table to fully outer position before resetting or undocking
* Do not set the lights above level 3
* Do not set the lights above level 3
== Manual operation ==
* Go to manual mode by pressing Stop: red lights on bore will turn on.
* Push the small safety handle/lever at the front bottom of the bed and push the bed in a few centimeters. Do this slowly!
* Pull the table back
* Press reset and retry normal operation
* Fully manual positioning: the bed is in the iso-center when aligned which the edge of the bore / 2nd pencil line on the bed.


== Undocking/docking the table ==
== Undocking/docking the table ==
Line 12: Line 20:
* Undock
* Undock


== Resetting table / manual operation ==
== Resetting table ==
In case the table operation does not respond:
In case the table operation does not respond, try the following options:
* Follow manual operation, see above
* Press the '''in''' button longer (~5 seconds). After a while the table goes into some sort of stand by mode, a long press can wake it up again.
* Press the '''in''' button longer (~5 seconds). After a while the table goes into some sort of stand by mode, a long press can wake it up again.
* Try stop/reset multiple times. Wait.
* Try stop/reset multiple times. Wait.
* 3-finger reset (takes 2 minutes). Wait. Repeated if needed.
* 3-finger reset (takes 2 minutes). Wait. Repeated if needed.
* Undock table (follow procedure above). Wait 1 minute before docking.
* Undock table (follow procedure above). Wait 1 minute before docking.
* Manual undocking: switch at lower right hand of the magnet:
* Manual undocking: upper switch at lower right hand of the magnet:
** up: undock - ''' careful: connector will come out of docking station! '''
** up: undock - ''' careful: connector will come out of docking station! '''
** center: ready to dock
** center: ready to dock
Line 24: Line 33:
* CDAS reset (see elsewhere on this wiki)
* CDAS reset (see elsewhere on this wiki)


If table beeps, bed position is lost, probably caused by not resetting not in outer bed position. Press Stop. Pull bed out manually. Follow reset procedure above.
If table beeps, bed position is lost, probably caused by not resetting not in outer bed position. Follow manual operation, see above.


If all fails, the table can be pushed in manually:
If all fails, the table can be pushed in manually:
* bed must be docked and connected.
* bed must be docked and connected.
* go to manual mode by pressing Stop: red lights on bore will turn on. Push the small safety handle/lever at the front bottom of the bed and push the bed in. Do this slowly!  
* go to manual mode by pressing Stop: red lights on bore will turn on. Push the small safety handle/lever at the front bottom of the bed and push the bed in. Do this slowly! Pushing the bed in usually requires two persons on each side.
The bed is in the iso-center when aligned which the edge of the bore / 2nd pencil line on the bed.
* The bed is in the iso-center when aligned which the edge of the bore / 2nd pencil line on the bed.
In all cases, call support, and/or Anton/Cor from Philips. Explain what was scanned/happened beforehand and report date/time.
In all cases, call support, and/or Anton/Cor from Philips. Explain what was scanned/happened beforehand and report date/time.


= Switching between systems =
== Troubleshooting table ==
 
[[Image:TableButtons.jpg|thumb|600px|Photo of table buttons]]
 
Instructions below can provide guidance when recovering from specific situations and are in addition to document “Instructions for Use Appendix: 7T FastTrak Couch” (part.num 4535 675 32953; doc id DMR124708). <br>
 
Follow this procedure with patience, and give the table controller time to react on your commands. <br>
In case of not responding motorized movement, try steps below. When table reacts on commands and
shows normal behavior, it not necessary to perform other steps in this procedure.
 
# First check if light, fan, music up/ down buttons (buttons#3-8) reacts;
# Press light up or down button (button#3 or 4) and hold for 2 seconds to wake the table controller from sleep mode.
#* Check if light, fan, music up/ down buttons (buttons#3-8) reacts;
# Press the stop button (button#1; big red) and reset button (button#2; small grey) and retry movement.
#* If necessary: retry this step 3 times;
# Press stop button (button#1 big red) and move table manually fully outwards. (Pull the table top all the way to the mechanical end).
#* Press reset button (button#2; small grey) and retry movement;
# Press stop button (button#1; big red) and move the table top manually fully outwards. (Pull the table top all the way to the mechanical end). Make sure that the full out LED (LED B) is on.
#* To reboot the table controller: Press ctrl+alt+del (button’s# 4, 6 & 8) and wait for battery LED  (LED C) to turn green.
#* In case of the LED (LED A) near the big red button is on, press stop (button#1; big red button) and reset (button#2; small grey);
# Press the stop button (button#1; big red) and move table manually fully outwards. (Pull the table top all the way to the mechanical end). Make sure that the full out LED (LED B) is on. Press the reset button (button#2; small grey) and retry movement;
# Press the stop button (button#1; big red) and move table manually fully outwards.
#* To reboot the table controller: Press ctrl+alt+del (button’s# 4, 6 & 8) and wait for battery LED (LED C) to turn green.
#* In case of LED (LED A) near big red button is on press (big red button and) reset (small grey);
# If all fails undock and dock and repeat this procedure (once) when necessary. <br>
In case of beep sound after a reboot: execute this procedure form step 3.
 
= Switching between 7T Achieva systems =


== Classic <-> MultiX ==
== Classic <-> MultiX ==
* No need for closing scanning environment
* Exit the scan environment of the system which was currently used (THIS STEP SEEMS OPTIONAL)
* Start '''logd'''
* Use '''Permproc stop scanner''' to disconnect the host being used from scanner.
* Start '''cmd'''. Run '''permproc stop scanner''' on both hosts. Monitor log-file. This doesn't take long. Run ''' permproc ''' to verify that scanner is not running.
* Unplug the rf-coil being used.
* Switch to other environment (using the switch next to scanner door)
* Switch to other environment (using the switch next to scanner door)
* Run '''permproc start scanner''' on new host.
* Use '''permproc start scanner''' on new host to be used.  
* Run '''logd''': CDAS will boot up. This takes 5-10 minutes. Wait for message: '''humidity of examination room'''
* Run '''logd''': CDAS will boot up. This takes 5-10 minutes. Wait for message: '''humidity of examination room''' (or '''NOMEASPARS''' in the logging browser)
* Meanwhile, connect coil if needed
* Meanwhile, connect the proper coil
 
 
== R5 <-> R3 ==
* Ensure that system is in Classic mode
* shut down R5 and R3 hosts. (Do not power down MultiX host).
* manually disconnect and connect cables. Do not use force, especially with large Philips cable! Slightly wiggle up/down. Important: put network cables back in correct ports (X25/X26).
* power up the new host: power button is on the back of the cabinet: carefully right-hand turn the cabinet to easily reach the back side.
* Login and start '''logd'''. Meanwhile, the CDAS will boot up, this takes 5-10 minutes. Wait for message: '''humidity of examination room'''
* Now start the Application software.
* Connect the proper coil/interface boxes


= System specific information =  
= System specific information =  
Line 60: Line 86:
Loading a patch:  
Loading a patch:  
* exit application software
* exit application software
* Start -> All Programs -> #PatchScripts# -> SmartPatch
* Run SmartPatch.pl from the Desktop
* '''logd''' wait for processes to finish then start software
* '''logd''' wait for processes to finish then start software
Installing patches: G:\Site\ClinicalScience\Put All Patches Here
Installing patches: G:\Site\ClinicalScience\Put All Patches Here
Line 69: Line 95:
** do NOT manually copy/paste/delete files in G:\patch. This directory links to the installation folder and will affect the installed patch files
** do NOT manually copy/paste/delete files in G:\patch. This directory links to the installation folder and will affect the installed patch files
* Shimtool: pride-folder should be present in G:\patch to automatically start shimtool as PRIDE process
* Shimtool: pride-folder should be present in G:\patch to automatically start shimtool as PRIDE process
=== MultiX ===
* Always have a classic host running for intercom communication
* SENSEref and CoilSurvey are automatically scanned whenever needed.


=== Classic (dualTx, R5B) ===
=== Classic (dualTx, R5B) ===
* Does NOT automatically scan SENSEref and CoilSurvey
* Does NOT automatically scan SENSEref and CoilSurvey
=== Making a new Reference Scan - Always Repeat Prescans ===
The scanner will always use the first valid reference scan for reconstruction. So for instance when removing patients from the scanner mid-session, a new reference scan needs to be made. Same goes for the case where the angulation of shimming of the reference scan was off.
Importantly, if a new reference scan is made, always select "'''Repeat Prescans'''" from the menu to make sure this new reference scan is used!


=== Errors ===
=== Errors ===
* Error: Coil coupling matrix abnormal. Caused by scanning phantoms. Scan Control Parameters --> Preparation --> CCM switch off. Apply (Do NOT save). Revert back after finishing scanning phantom.
* The MTX-Volume-T/R-coil needs 4500 watts where 3800 watts is allowed
 
B1 cannot be reached, lower value (to 17, 15 or lower, set to 15 in example below):
 
Check Contrast --> B1 mode: change from Default to 15.
 
For T1, FLAIR, MP(2)RAGE and other scans with inversion pulses: check Contrast --> Inversion control: max B1 (uT). Set to same value as B1 mode (also 15).


== R3 ==
To find the detailed error message: Use logging application or log browser to query log file. Reported in log file as 'Average Forward Power Fault'.  
=== usage ===
==== stop/start all processes (NB including data transfer!)====
* '''permproc stop|start all''' stop|start all processes
* '''c:\nmr\gyroscan\commands\activate_configuration.pl'''. type y, Enter.
* '''start_stop_procs.pl stop''' also stops background processes. Needed in case of hardware reset in service room.
==== Communication with PRIDE (e.g. for image-based shimming):====
* '''PrideXS_XML'''. In case of error ''Access denied, no SW key pressed'', kill process pridexsproc_win_cs.exe in Task Manager.
==== Export raw data: ====
* System --> Advanced tools --> Delayed reconstruction. 'Select exam', type number of exam. Click 'Prev Scans'. 'Type 2'. Select 'Raw Export'. Now type the number of your series. Click Proceed. Type a number to save your series under. (Choose a different one for each series to avoid overwriting earlier ones). Type Enter/Proceed a few times. Now the scan is added to the scan list. You can add more series to reconstruct or continue, by clicking Start Scan and click Proceed.
*When finished click 'Exit' to release this scan to the scanner database again. Your data will appear under G:\Temp (sort by date to find it) as raw_00XX.list / raw_00XX.data where XX is the number you gave it earlier.
*'''Note''' that this doesn't work under the MISS patch (version oct 2015). You can, however, export raw MISS data by removing the patch and then following the steps described above.
*Alternatively use gt pack 'n go utility. This requires ReconFrame (which we don't have yet) and licensed matlab software to reconstruct raw data. Note that this tool does not export the same raw data format.
==== Location shim parameters: ====
* '''E:\Export\PRIDE\shimtool\linear_shim.txt'''
==== Manually selecting coil elements: ====
* Control Parameter Editor - Scan (approx 1/3, 6x clicking):
* User def. channel selection - yes
* at initial, Xmit Coil selection. choose 0.
* Dual coil - No. (2e surface coil off, independent selection per surface coil not possible)


==== Direct protocol comparison  ====
One should try not to change the ref scales in System Tuning - however if you do, then keep the RATIO the same between the two ref scales for the two transmit channels (on Classic).
* Export exam card with the protocols you want to compare.
* Do this:
[[Image:Compareprotocols.jpg|200px]]


==== Delayed Reconstruction ====
* Coil parameters are not set correctly. Perhaps not added to a patch? Check settings above.
* User def element selection: yes
* selecteer elementen: waarde 1


==== Saving and loading configuration file ====
* Occasionally, the host pc will go into a setup mode on booting (see image). Press escape to return to windows.
* MRService inloggen
[[File:Error1.png|thumb|pop-up window - avoid by pressing escape]]
* MR Applications - Service tools - Export configuration
* Enter (na afsluiten software)  
* Choose 1 for internal disk to write to (I - make new folder (no spaces))
* As directory I fills up quickly, it's probably a good idea to replace the configuration directory that's already there.


* To reset configuration to previous : MR Applications - Service tools - Import configurations
*  


==== Changed default settings ====
*
* Control parameter Reconstruction: Noise clip factor 1,2,3: 0.001. Avoids noise clipping of phase to -pi in case the SNR is too low.
 
* Go to System Tuning, Tuned Hardware. HIGH RF aux drive scale: 0.7915 en 0.8572. Philips Service tuned these parameters to 0.8542 en 0.9252. These values were reduced by sqrt(15%), this is because the logged power deviates from what the PMU (in the technical room) displays. The value can be read while the scanner is running a sequence. Setting stored by Maarten Versluis (2016-03-02), MV: updated calibrated DS.
== MultiX ==
* System Tuning -> Coil. Select Coil T/R-Vol-MTX (also Coil T/R-Vol?). Ref scales 1&2: default is 0.1884&0.1914. Adjust to 0.25
* Always have a classic host running for intercom communication
* SENSEref and CoilSurvey are automatically scanned whenever needed.


==== Patches ====
Tx testing:
* Increased maximum average power to 20:
System Tuning --> Coil --> NOVA Head coil
** '''max_avg_pow: 20''' in '''mpgcoil_volume_tr_mtx.i''' and '''mpgcoil_volume_tr.i''', add file to patch folder to apply. Check Coil parameters and log file (search for PMU), check that system is not using  the default value of 15!
Transmit phases: 0, -45, -90, ..., -315
CCM-file, Datamonitoring tab --> CCM. Make screen shot when scanning.


==== Scanning sequences ====
=== MRCodetool ===
* B1 mode: 17 uT (dus niet op default). 20 uT wordt bijna nooit gehaald in vrijwilligers (zie data monitoring), de fliphoek moet na PO groter dan 80 graden zijn!
* B0 scan includes Exportdata pride tool
* Preparation phases: full (dus niet auto). Bij auto wordt de pickup-coil drive scale gekozen, als de power optimization failed, wordt dit de default waarde plus safety margin = 0.19 + 25% = 0.23. Dit resulteert in half vermogen, dus halve B1!
* start menu/desktop to open tool (installed in E:\Export\MRCodeTool)
* run unshimmed B0 to shim on
=> run B0shimming in MRCodeTool
* run shimmed B0 (for the B1 shim)
* FFE dyn scan (acquires FFE transmitting on each channel - output 8 images - input for B1 shimming)
* FFE quad scan (all 8 in quadrature - workaround for bug)
* B1 quad (B1 map (DREAM) - input for B1 shimming)
=> run RFshimming in MRCodeTool (minimizes standard deviation B1 over single (centre?) slice)
* in scans where you want to use the rf-shim, select contrast-rfshim-shimtool
* contrast-rfshim-predefined offers pre-calculated options (on models)
For SPINS pulses:
* B1map dyn (B1 map (DREAM leaving every run 1 channel out) - input for SPINS pulse calculation in addition to the above)
* Open the protocol you'd like to use your pulse in, change MTX pulse def id. to a non-used number (check on G:\Site\Waveforms)
* confirm that the protocol gives a conflict (non existing pulse)
* run SPINS module in MRCode
* confirm that protocol is no longer in conflict (pulse now exists)
* run scan
For MP2RAGE:
* load MP2RAGE protocol
* change end_rep_delay to desired value **NEEDS UPDATING**
* run MP2RAGE prot MRCode


=== Errors ===
=== Errors ===
* Error: Coil coupling matrix abnormal. Caused by scanning phantoms. Scan Control Parameters --> Preparation --> CCM switch off. Apply (Do NOT save). Revert back after finishing scanning phantom.
= Software =
== MRCodeTool (B0 shim) ==
The B0 shim from MRCode is included as a PRIDE job under the actual B0 scan. It crashes regularly and its progress/success should always be monitored. You should see three matlab windows appearing with (1) your B0 map (2) the brain-extracted B0 map and (3) a histogram of field values. The bottom histogram should show a narrower distribution than the top one. If this 3rd window did not appear, your shim did not succeed and you should not continue scanning.
For all MRCodeTool modules, including the shimming one, you can use the following:
* ''The window opens but nothing happens:'' press ctrl-alt-delete, remove the PulseClient and PulseServer processes, start a second PRIDE job. To add a PRIDE job, right-click on the scan (not on the failed job), choose PRIDE Research, B0map (or other) and proceed. Monitor progress. Check under the contrast tab that the shim values have been read in.
* ''The PRIDE job crashes straightaway (red cross):'' Most likely the pride process has crashed. Open a command window, type "permproc" and look for ProcessingService. If it is "not running", type ''permproc start ProcessingService''. Then start a new pride job. Monitor progress. Check under the contrast tab that the shim values have been read in.
* ''Killed PulseClient but still nothing happens: '' Time to reboot PRIDE. Open a command window, type ''permproc stop ProcessingService'' (confirm that job has now crashed) and then ''permproc start ProcessingService''; make a new PRIDE job. (In this case, it really is safer not to copy the crashed one). Monitor progress. Check under the contrast tab that the shim values have been read in.
=== poor shim results ===
If the phase unwrapping of the B0 map is not complete, then the MRCodeTool module will not be able to find a good shim solution. You may notice the remaining phase wrap in the popup images, or you may simply have a terrible EPI image as a result. If this happens, you can do two things:
* calculate the shim using Compass (start Compass.exe, choose tools, choose B0-mapping, enter input filename ('G:/patch/pride/tempinputfiles, I think), hit 'run')
* re-run the B0-map with a smaller deltaTE. 0.8ms instead of 1 is usually enough.


==== Scan aborted after error ====
== MRCodeTool (MP2RAGE) ==
* B1 cannot be reached. Lower B1 (in Contrast tab) from Default to 17,15, or 10.
* Coil parameters are not set correctly. Perhaps not added to a patch? Check settings above.


==== Not enough signal in PU phase ====
The MRCodeTool can deal with two types of MP2RAGEs: those acquired with the MISS (including T123DEPI and MP2RAGEME data and everything acquired with FatNavs) and those acquired with all other patches, also known as the 'cardiac phases' MP2RAGE.


Read section Scanning sequences above and check sequence settings B1 mode and Preparation phase.
* MP2RAGE (1 scan, all patches but MISS)
Use the MP2RAGE job. Only the PRIDE jobs will write data into the database (not the gui). The parameters for the T1-maps are taken from the file starting with variablesettings_... in E/Export/MRCodeTool/PulseClient/. Make sure you use variablesettings_clean.txt. If the file contains lines with 'inversiontime' then remove the file and replace it with original_variablesettings_clean.txt.
The T1-weighted image and T1map can be viewed from the images tab on the scanner (i.e. not the list view).  


Check the drive scale (ref scale).
* MISS MP2RAGE (multiple scans)
Right mouse button on remaining scanning time -> System Tuning -> Coil. Select Coil T/R-Vol-MTX, Coil T/R-Vol. Ref scales 1&2: possibly are 0.1884&0.1914. Adjust to 0.25. Stepwise increase to 0.28 and 0.30 if problem persists.  
Two jobs are required: 1 export job on MP2RAGE_INV1 and 1 mp2rage (2 inputs) on MP2RAGE_INV2. Note that MP2RAGE_INV2 is typically the first scan in the queue. You need to select the right set of settings for your acquisition and rename the wanted .txt file to variable_settings_SOMETHINGRELEVANT.txt. Please put back the clean one after you finish!
If there is no variablesettings file for your experiment, you can quite easily make one following the instructions below:
FIRST_inversiontime_sec = inversion time MP2RAGE_INV1 / 1000 (because this is required in seconds but specified in milliseconds).  
SECOND_inversiontime_sec = (shot_interval MP2RAGE_INV1 + 0.5*TFE_dur_shot/acq(ms) MP2RAGE_INV2 )/1000
MP2RAGE_repetitionTime_sec = shot_interval MP2RAGE_INV1/1000 + shot_interval MP2RAGE_INV2/1000 + dyn scan time FATNAV (if present).


Alternatively, you can turn off the pick up coil optimization by taking the following steps (however, this might have an effect on your data!):
== delayed reconstruction ==
* Select Control Parameter Editor
* Select the tab Preparation
* Select off for Pick up coil optimization
* Click apply


==== Scan aborts after 30 seconds ====
Under R5 the data can be reconstructed (post-scanning) using some different recon parameters. Useful if you'd like to save also the separate coil images, calculate g-factors or interpolate differently. Raw data saving does need to be switched on, obviously.
Average power is too high. Probably a scan with high SAR. Check that max average power is increased from 15 to 20 (see above).


# On the post-processing tab of your protocol, switch on raw data saving
# Following running of the scan, right-click on finished scan -> delayed reconstruction
# Open the job it puts under your scan
# Edit the parameters you would like to change(matrix size, saving separate coils, etc)
# remove the waiting thingy.
# wait. enjoy.


= Software =
== B1 shimming ==
== B1 shimming ==
* Export B1 as parrec and load in RFshimGUI
* Export B1 as parrec and load in RFshimGUI
Line 171: Line 220:


=== MultiX ===
=== MultiX ===
Scan cycled FFE. Set Multichannel images: no (not supported by RFShimGUI)
Export as PARREC


single B1+ maps
Built-in RF shimming is (currently) done on the phase only: Relative Phase Nulling. The result is a phase difference, by which the coil transmit phases are adjusted. The scanner adds the RF shim angles (centered around 0) to  Coil Tx phases. Search for "TransmitPhase" in the log file to find the shim results.
dyn relative B1 maps
 
Single Slice
Manual shimming: Scan cycled FFE. Set Multichannel images: no (not supported by RFShimGUI). Export as PARREC
 
single B1+ maps. dyn relative B1 maps. Single Slice.
 
== license updates ==
 
Once a year (feb 15th) the license file expires on the scanners. Should you need to update the licenses, follow these steps (R5 specific):
1) open the Service Application
2) fill in your name and reason for entry
3) under software options, choose update license file
4) select OK
 
== Splitting/averaging DTI series ==
 
[[Splitting DTI]]


= (Common) errors, malfunctions and fixes=
= (Common) errors, malfunctions and fixes=
== Software ==
===halfscan in EPI===
The EPI's (as used in functional imaging) are filtered in a post-processing step which causes signal loss in places with phase jumps. These are especially detrimental in areas with poor local shimming such as over the sinusses and ear canals. If you switch off the filtering, the artefacts disappear.
To do this, one needs to:
* open the Sequence Development Editor
* In the tab Parameters, scroll down to RC, double click
* On the right panel:
* partial_matrix_filters: switch off (only 2nd element)
* part_filt_window_np_dir and part_filt_window_p_dir set to 0
To do: perhaps only one of these options is required


= Hardware =
===PRIDE jobs hanging===
SHIMTOOL/MRCODETOOL, pride crash
* Close Application software
* run 'permproc stop ProcessingService'
* empty <G:\queue\> folder
* run 'permproc start ProcessingService'
* Restart Application software and create new examination


== Errors ==
== Hardware ==
===No trigger===
===No trigger===
* Check if your sequence is sending triggers (sync external device ON)
* Check if sync box on console pc has power (right LED green)
* Check if sync box on console pc has power (right LED green)
* Unplug/replug power.
* Unplug/replug power.
Line 190: Line 269:
* coldhead compressors
* coldhead compressors
* gradient amplifiers
* gradient amplifiers
===No power in bed, won't dock, no 'air puffs'===
===No power in bed, won't dock, no 'air puffs'===
* Probably no air pressure
* Probably no air pressure
* Check meters in cabinet at the back of CDAS (remove panel using imbus size 5)
* Check if compressor in climate control room on office level is running (compressor located on the left, right after entrance). Pressure should be about 8 bar. Start with switch if pressure is low [picture to be uploaded]. Pressure takes minutes to build up.
* Check meters in cabinet at the back of CDAS (how to remove panel? Ask Cor/Anton).
* Pressure meters should look approx. like this: [picture to be uploaded]
* Pressure meters should look approx. like this: [picture to be uploaded]
===No physiologic signals being logged===
===No physiologic signals being logged===
* Check if all sensors are plugged in, at least ECG!
* Check if all sensors are plugged in, at least ECG!
Line 201: Line 283:
Irregular 'cracking noise' in scanner room. Originates from shim rack.
Irregular 'cracking noise' in scanner room. Originates from shim rack.
=== Not all scanner functions available ===
=== Not all scanner functions available ===
Might have an error in shim gradients.
Might have an error in shim gradients (HOS error or fault, i.e. higher order shimming).
For reset:
For reset:
* Enter on the computer: "permproc stop scanner"
* Enter on the computer: "permproc stop scanner"
* Turn off the 3 switches (at the bottom) of the shim gradients in the technical room. Turn off in following order: Left, right, middle and wait a couple of seconds
* Turn off the 3 switches (at the bottom) of the shim gradients in the technical room. Turn off in following order: Middle, Right, Left and wait a couple of seconds
* Turn on the 3 switches in reversed order
* Turn on the 3 switches in reversed order
* Enter on the computer: "permproc start scanner"
* Enter on the computer: "permproc start scanner"


=== Defect in shim gradients ===
=== Airflow in magnet bore is insufficient (typically after bi-monthly emergency power test) ===
 
Caused by the building's climate control system not rebooting, resulting in too limited airflow to the scanners. Call 88, describe the problem!
Irregular 'cracking noise' in scanner room. Originates from shim rack.


===  gradients overheating ===
For certain protocols, the gradients may approach their critical temperature (65 degrees). When this happens, the scan will abort and you will have to wait until the gradients have cooled down completely (~30 minutes). To avoid this, you can switch on the multimeter on the desk (set to Volt) and monitor the temperature while you scan. The reported value is temperature in degrees C/10. E.g. 5.5 means the gradients are at 55 degrees.


== Power off and power on sequence(s) ==
== Power off and power on sequence(s) ==
Line 227: Line 310:


=== Main System ===
=== Main System ===
* Printed out instructions are in right mains cabinet in technical room:
* [[Media:20170628_Power_down_7T.pdf|A printed copy of the instructions]] are in right mains cabinet in technical room.
[[File:7T powerdown instructions.jpg|200px|7t powerdown instructions]]
* old instructions: [https://www.spinozacentre.nl/wiki2/images/2/25/7T_powersequence_Leiden.pdf Leiden document (original in scstaff)]


=== Compressors ===
=== Compressors ===
Line 241: Line 322:


Box hanging the CDAS rack. Turn off by unplugging 220V cable.
Box hanging the CDAS rack. Turn off by unplugging 220V cable.


== Coil-specific tips 'n tricks ==
== Coil-specific tips 'n tricks ==
Line 249: Line 329:


== BOLD screen ==
== BOLD screen ==
Turn on by connecting the power cable in the black adapter in the technical room. Turn off after use!
Turn on by switching the switch in the console room to ON. Turn off after use!
The visibility range in the vertical direction is from -4 to +3 on the desktop image. This means that at the top ~10% of the screen cannot be used.
The visibility range in the vertical direction is from -4 to +3 on the desktop image. This means that at the top ~10% of the screen cannot be used.


= Contact information =
= Contact information =
== Philips contacts (?) ==
== Philips contacts ==


Cor Romeijn: 06 22489509
Anton Heijmans:  06 22491918
Anton Heijmans:  06 22491918
Maarten Versluis: 06 11386561
Maarten Versluis: 06 11386561
Line 270: Line 349:
= QA =
= QA =


Run QA on Classic R5.
QA has moved here: '''[[7TQA|7T MRI Quality assurance]]*'''
 
== FID QA measurements ==
This procedure repeatedly measures the 8th sample of a pulse-acquire FID measurement, using proton and multi-nuclei amplifiers, with and without gradients.
Creator: Paul Sanders, Philips
 
* Position blue phantom sphere in center of 32ch head coil, use holder. Make sure the phantom is centered.
* Remove any installed patch
** The application software might not show that there is a patch active, but if the 'G:\Patch\' folder contains files, there is a patch installed.
** Open SmartPatch and press 1. This will take a while.
* Perform a prescan : QA\QA_FID_Survey
** Scan a survey. Click OK on the following message: 'Cannot determine optimum RF power'.
* Application software can be on, but list of planned scans must be empty.
 
 
=== Scanning procedure ===
* double click '''G:\TA\Testscripts\sc_fids\start_fid_stability_*.bat''' to start scanning. A command window appears. Be patient, don't close windows. Batch Interpreter window appears and disappears. After 2 minutes, turn on patient communication to verify that you here repeating 'ticks'.
* After approx. 5 minutes a PlotServer window appears with results. During scanning, more tabs/pages with results appear. Scanning finishes after ~20 minutes. In command window it says: 'press any key to continue'. Click space bar, this ends the measurement.
 
=== PlotServer ===
* In each tab/result window, right mouse click (anywhere) --> reset.
* Tab1 Mod profile: shows FID for all measurements
* Other tabs plot the repeated 8th sample of FID for all 32 channels. Horizontal axis: repeated measure (512 or 1024). 150ms between measurements.
** measurement 250-275: programmed 1% lower signal as a reference
** first 16: box A (lower). last 16: box B. (border between magenta/purple and cyan/lightblue)
** Gr=true/false: gradients on/off. MN (multi-nuclei) or PR (proton) amplifier.
 
=== Save output ===
* Copy folder '''G:\TA\fid_stab\7t-acq_DATE''' to S:\7T_QA\FID (\\ftpsc\DATA\scdropbox\7T_QA\FID)
* Zip output folder: right-mouse button, 7-Zip->Add to 7t-acq-DATE.zip
* Delete output-folder G:\TA\fid_stab\7t-acq_DATE
 
=== Offline processing ===
to make QA plots:
Start MATLAB (e.g. on ftpsc) and run matlab-script '''scdropbox/7T_QA/FID/software/fid/fid_stab_viewer_v4.m'''. A file prompt appears, open one .txt file in the output folder. Now all plots for all output-files in this directory are generated.
 
=== Various ===
* software is installed in G:\TA (Ruby language, .rb files)
* double click G:\TA\Ruby193\start_ruby193*.bat to start Ruby
 
* sc_fid_stability_r5_v1.rb
**lines 21:24: (Only_grad_switching) true: run with gradient switching. false: one times without, one time with gradients.
** Start_pr_rf_amp: first PR then MN amplifier. false: start with MN
** repeat_per_tests --> 1024
 
* sc_fid_stability_r5_v1.rb
** lines 292 pulse-acquire scan
** 300-307: add gradient blocks (objects are removed based on only_grad_switching setting)
** 308 RF0 RF-pulse
** 309 AQ0 acquire FID signal
 
load files to view/verify:
* (drag G:\TA\Testscripts\sc_fids\start_fid_stability*.bat into Ruby window (not so interesting))
 
=== Logbook ===
20161011 MC: MN with gradients 3rd channel: spurious spikes of 1%

Latest revision as of 10:36, 27 June 2022

Overview page for 7T Achieva related information

Table operation

  • When pulling the table out, stop when 'table out' LED turns on. Don't pull further than backside of bed. When undocking, the bed will be pushed back the remaining centimeter.
  • Move table to fully outer position before resetting or undocking
  • Do not set the lights above level 3

Manual operation

  • Go to manual mode by pressing Stop: red lights on bore will turn on.
  • Push the small safety handle/lever at the front bottom of the bed and push the bed in a few centimeters. Do this slowly!
  • Pull the table back
  • Press reset and retry normal operation
  • Fully manual positioning: the bed is in the iso-center when aligned which the edge of the bore / 2nd pencil line on the bed.

Undocking/docking the table

Warning: not following the right undocking procedure will damage the equipment!

  • When scanning with dualTx: Disconnect cables and remove interface boxes
  • Pull table pins up (ensure they stay up)
  • Undock

Resetting table

In case the table operation does not respond, try the following options:

  • Follow manual operation, see above
  • Press the in button longer (~5 seconds). After a while the table goes into some sort of stand by mode, a long press can wake it up again.
  • Try stop/reset multiple times. Wait.
  • 3-finger reset (takes 2 minutes). Wait. Repeated if needed.
  • Undock table (follow procedure above). Wait 1 minute before docking.
  • Manual undocking: upper switch at lower right hand of the magnet:
    • up: undock - careful: connector will come out of docking station!
    • center: ready to dock
    • down: dock(?)
  • CDAS reset (see elsewhere on this wiki)

If table beeps, bed position is lost, probably caused by not resetting not in outer bed position. Follow manual operation, see above.

If all fails, the table can be pushed in manually:

  • bed must be docked and connected.
  • go to manual mode by pressing Stop: red lights on bore will turn on. Push the small safety handle/lever at the front bottom of the bed and push the bed in. Do this slowly! Pushing the bed in usually requires two persons on each side.
  • The bed is in the iso-center when aligned which the edge of the bore / 2nd pencil line on the bed.

In all cases, call support, and/or Anton/Cor from Philips. Explain what was scanned/happened beforehand and report date/time.

Troubleshooting table

Error creating thumbnail: File missing
Photo of table buttons

Instructions below can provide guidance when recovering from specific situations and are in addition to document “Instructions for Use Appendix: 7T FastTrak Couch” (part.num 4535 675 32953; doc id DMR124708).

Follow this procedure with patience, and give the table controller time to react on your commands.
In case of not responding motorized movement, try steps below. When table reacts on commands and shows normal behavior, it not necessary to perform other steps in this procedure.

  1. First check if light, fan, music up/ down buttons (buttons#3-8) reacts;
  2. Press light up or down button (button#3 or 4) and hold for 2 seconds to wake the table controller from sleep mode.
    • Check if light, fan, music up/ down buttons (buttons#3-8) reacts;
  3. Press the stop button (button#1; big red) and reset button (button#2; small grey) and retry movement.
    • If necessary: retry this step 3 times;
  4. Press stop button (button#1 big red) and move table manually fully outwards. (Pull the table top all the way to the mechanical end).
    • Press reset button (button#2; small grey) and retry movement;
  5. Press stop button (button#1; big red) and move the table top manually fully outwards. (Pull the table top all the way to the mechanical end). Make sure that the full out LED (LED B) is on.
    • To reboot the table controller: Press ctrl+alt+del (button’s# 4, 6 & 8) and wait for battery LED (LED C) to turn green.
    • In case of the LED (LED A) near the big red button is on, press stop (button#1; big red button) and reset (button#2; small grey);
  6. Press the stop button (button#1; big red) and move table manually fully outwards. (Pull the table top all the way to the mechanical end). Make sure that the full out LED (LED B) is on. Press the reset button (button#2; small grey) and retry movement;
  7. Press the stop button (button#1; big red) and move table manually fully outwards.
    • To reboot the table controller: Press ctrl+alt+del (button’s# 4, 6 & 8) and wait for battery LED (LED C) to turn green.
    • In case of LED (LED A) near big red button is on press (big red button and) reset (small grey);
  8. If all fails undock and dock and repeat this procedure (once) when necessary.

In case of beep sound after a reboot: execute this procedure form step 3.

Switching between 7T Achieva systems

Classic <-> MultiX

  • Exit the scan environment of the system which was currently used (THIS STEP SEEMS OPTIONAL)
  • Use Permproc stop scanner to disconnect the host being used from scanner.
  • Unplug the rf-coil being used.
  • Switch to other environment (using the switch next to scanner door)
  • Use permproc start scanner on new host to be used.
  • Run logd: CDAS will boot up. This takes 5-10 minutes. Wait for message: humidity of examination room (or NOMEASPARS in the logging browser)
  • Meanwhile, connect the proper coil

System specific information

R5

Patches

Loading a patch:

  • exit application software
  • Run SmartPatch.pl from the Desktop
  • logd wait for processes to finish then start software

Installing patches: G:\Site\ClinicalScience\Put All Patches Here

General

  • SmartPatch:
    • after switching patches, WAIT for loading all boards etc. before starting application software. Inspect PatchReadyCheck tool
    • do NOT manually copy/paste/delete files in G:\patch. This directory links to the installation folder and will affect the installed patch files
  • Shimtool: pride-folder should be present in G:\patch to automatically start shimtool as PRIDE process

Classic (dualTx, R5B)

  • Does NOT automatically scan SENSEref and CoilSurvey

Making a new Reference Scan - Always Repeat Prescans

The scanner will always use the first valid reference scan for reconstruction. So for instance when removing patients from the scanner mid-session, a new reference scan needs to be made. Same goes for the case where the angulation of shimming of the reference scan was off. Importantly, if a new reference scan is made, always select "Repeat Prescans" from the menu to make sure this new reference scan is used!

Errors

  • The MTX-Volume-T/R-coil needs 4500 watts where 3800 watts is allowed

B1 cannot be reached, lower value (to 17, 15 or lower, set to 15 in example below):

Check Contrast --> B1 mode: change from Default to 15.

For T1, FLAIR, MP(2)RAGE and other scans with inversion pulses: check Contrast --> Inversion control: max B1 (uT). Set to same value as B1 mode (also 15).

To find the detailed error message: Use logging application or log browser to query log file. Reported in log file as 'Average Forward Power Fault'.

One should try not to change the ref scales in System Tuning - however if you do, then keep the RATIO the same between the two ref scales for the two transmit channels (on Classic).

  • Coil parameters are not set correctly. Perhaps not added to a patch? Check settings above.
  • Occasionally, the host pc will go into a setup mode on booting (see image). Press escape to return to windows.
Error creating thumbnail: File missing
pop-up window - avoid by pressing escape

MultiX

  • Always have a classic host running for intercom communication
  • SENSEref and CoilSurvey are automatically scanned whenever needed.

Tx testing: System Tuning --> Coil --> NOVA Head coil Transmit phases: 0, -45, -90, ..., -315 CCM-file, Datamonitoring tab --> CCM. Make screen shot when scanning.

MRCodetool

  • B0 scan includes Exportdata pride tool
  • start menu/desktop to open tool (installed in E:\Export\MRCodeTool)
  • run unshimmed B0 to shim on

=> run B0shimming in MRCodeTool

  • run shimmed B0 (for the B1 shim)
  • FFE dyn scan (acquires FFE transmitting on each channel - output 8 images - input for B1 shimming)
  • FFE quad scan (all 8 in quadrature - workaround for bug)
  • B1 quad (B1 map (DREAM) - input for B1 shimming)

=> run RFshimming in MRCodeTool (minimizes standard deviation B1 over single (centre?) slice)

  • in scans where you want to use the rf-shim, select contrast-rfshim-shimtool
  • contrast-rfshim-predefined offers pre-calculated options (on models)

For SPINS pulses:

  • B1map dyn (B1 map (DREAM leaving every run 1 channel out) - input for SPINS pulse calculation in addition to the above)
  • Open the protocol you'd like to use your pulse in, change MTX pulse def id. to a non-used number (check on G:\Site\Waveforms)
  • confirm that the protocol gives a conflict (non existing pulse)
  • run SPINS module in MRCode
  • confirm that protocol is no longer in conflict (pulse now exists)
  • run scan

For MP2RAGE:

  • load MP2RAGE protocol
  • change end_rep_delay to desired value **NEEDS UPDATING**
  • run MP2RAGE prot MRCode

Errors

  • Error: Coil coupling matrix abnormal. Caused by scanning phantoms. Scan Control Parameters --> Preparation --> CCM switch off. Apply (Do NOT save). Revert back after finishing scanning phantom.

Software

MRCodeTool (B0 shim)

The B0 shim from MRCode is included as a PRIDE job under the actual B0 scan. It crashes regularly and its progress/success should always be monitored. You should see three matlab windows appearing with (1) your B0 map (2) the brain-extracted B0 map and (3) a histogram of field values. The bottom histogram should show a narrower distribution than the top one. If this 3rd window did not appear, your shim did not succeed and you should not continue scanning.

For all MRCodeTool modules, including the shimming one, you can use the following:

  • The window opens but nothing happens: press ctrl-alt-delete, remove the PulseClient and PulseServer processes, start a second PRIDE job. To add a PRIDE job, right-click on the scan (not on the failed job), choose PRIDE Research, B0map (or other) and proceed. Monitor progress. Check under the contrast tab that the shim values have been read in.
  • The PRIDE job crashes straightaway (red cross): Most likely the pride process has crashed. Open a command window, type "permproc" and look for ProcessingService. If it is "not running", type permproc start ProcessingService. Then start a new pride job. Monitor progress. Check under the contrast tab that the shim values have been read in.
  • Killed PulseClient but still nothing happens: Time to reboot PRIDE. Open a command window, type permproc stop ProcessingService (confirm that job has now crashed) and then permproc start ProcessingService; make a new PRIDE job. (In this case, it really is safer not to copy the crashed one). Monitor progress. Check under the contrast tab that the shim values have been read in.

poor shim results

If the phase unwrapping of the B0 map is not complete, then the MRCodeTool module will not be able to find a good shim solution. You may notice the remaining phase wrap in the popup images, or you may simply have a terrible EPI image as a result. If this happens, you can do two things:

  • calculate the shim using Compass (start Compass.exe, choose tools, choose B0-mapping, enter input filename ('G:/patch/pride/tempinputfiles, I think), hit 'run')
  • re-run the B0-map with a smaller deltaTE. 0.8ms instead of 1 is usually enough.

MRCodeTool (MP2RAGE)

The MRCodeTool can deal with two types of MP2RAGEs: those acquired with the MISS (including T123DEPI and MP2RAGEME data and everything acquired with FatNavs) and those acquired with all other patches, also known as the 'cardiac phases' MP2RAGE.

  • MP2RAGE (1 scan, all patches but MISS)

Use the MP2RAGE job. Only the PRIDE jobs will write data into the database (not the gui). The parameters for the T1-maps are taken from the file starting with variablesettings_... in E/Export/MRCodeTool/PulseClient/. Make sure you use variablesettings_clean.txt. If the file contains lines with 'inversiontime' then remove the file and replace it with original_variablesettings_clean.txt. The T1-weighted image and T1map can be viewed from the images tab on the scanner (i.e. not the list view).

  • MISS MP2RAGE (multiple scans)

Two jobs are required: 1 export job on MP2RAGE_INV1 and 1 mp2rage (2 inputs) on MP2RAGE_INV2. Note that MP2RAGE_INV2 is typically the first scan in the queue. You need to select the right set of settings for your acquisition and rename the wanted .txt file to variable_settings_SOMETHINGRELEVANT.txt. Please put back the clean one after you finish! If there is no variablesettings file for your experiment, you can quite easily make one following the instructions below: FIRST_inversiontime_sec = inversion time MP2RAGE_INV1 / 1000 (because this is required in seconds but specified in milliseconds). SECOND_inversiontime_sec = (shot_interval MP2RAGE_INV1 + 0.5*TFE_dur_shot/acq(ms) MP2RAGE_INV2 )/1000 MP2RAGE_repetitionTime_sec = shot_interval MP2RAGE_INV1/1000 + shot_interval MP2RAGE_INV2/1000 + dyn scan time FATNAV (if present).

delayed reconstruction

Under R5 the data can be reconstructed (post-scanning) using some different recon parameters. Useful if you'd like to save also the separate coil images, calculate g-factors or interpolate differently. Raw data saving does need to be switched on, obviously.

  1. On the post-processing tab of your protocol, switch on raw data saving
  2. Following running of the scan, right-click on finished scan -> delayed reconstruction
  3. Open the job it puts under your scan
  4. Edit the parameters you would like to change(matrix size, saving separate coils, etc)
  5. remove the waiting thingy.
  6. wait. enjoy.

B1 shimming

  • Export B1 as parrec and load in RFshimGUI
  • Copy rfshims.dat from D: to G:\Site
  • RF Shims: shimtool

MT B1 calibration scan scan UI --> full enables editing B1-scan parameters B1 field map: yes --> makes image instead of calibration scan

Text in log files: Reading G:\site\rfshims.dat am_scales=..., phases = 0 11

If RFshimGUI doesn't start (error: Undefined function or variable matlabrc), clear cache folder G:\Temp\Gyrotest\MCRCache

MultiX

Built-in RF shimming is (currently) done on the phase only: Relative Phase Nulling. The result is a phase difference, by which the coil transmit phases are adjusted. The scanner adds the RF shim angles (centered around 0) to Coil Tx phases. Search for "TransmitPhase" in the log file to find the shim results.

Manual shimming: Scan cycled FFE. Set Multichannel images: no (not supported by RFShimGUI). Export as PARREC

single B1+ maps. dyn relative B1 maps. Single Slice.

license updates

Once a year (feb 15th) the license file expires on the scanners. Should you need to update the licenses, follow these steps (R5 specific): 1) open the Service Application 2) fill in your name and reason for entry 3) under software options, choose update license file 4) select OK

Splitting/averaging DTI series

Splitting DTI

(Common) errors, malfunctions and fixes

Software

halfscan in EPI

The EPI's (as used in functional imaging) are filtered in a post-processing step which causes signal loss in places with phase jumps. These are especially detrimental in areas with poor local shimming such as over the sinusses and ear canals. If you switch off the filtering, the artefacts disappear. To do this, one needs to:

  • open the Sequence Development Editor
  • In the tab Parameters, scroll down to RC, double click
  • On the right panel:
  • partial_matrix_filters: switch off (only 2nd element)
  • part_filt_window_np_dir and part_filt_window_p_dir set to 0

To do: perhaps only one of these options is required

PRIDE jobs hanging

SHIMTOOL/MRCODETOOL, pride crash

  • Close Application software
  • run 'permproc stop ProcessingService'
  • empty <G:\queue\> folder
  • run 'permproc start ProcessingService'
  • Restart Application software and create new examination

Hardware

No trigger

  • Check if your sequence is sending triggers (sync external device ON)
  • Check if sync box on console pc has power (right LED green)
  • Unplug/replug power.
  • table
  • coldhead compressors
  • gradient amplifiers

No power in bed, won't dock, no 'air puffs'

  • Probably no air pressure
  • Check if compressor in climate control room on office level is running (compressor located on the left, right after entrance). Pressure should be about 8 bar. Start with switch if pressure is low [picture to be uploaded]. Pressure takes minutes to build up.
  • Check meters in cabinet at the back of CDAS (how to remove panel? Ask Cor/Anton).
  • Pressure meters should look approx. like this: [picture to be uploaded]

No physiologic signals being logged

  • Check if all sensors are plugged in, at least ECG!
  • Check if ECG sensor has (working) battery
  • If this is OK, switch CDAS off/on (after switching off host!)

Defect in shim gradients

Irregular 'cracking noise' in scanner room. Originates from shim rack.

Not all scanner functions available

Might have an error in shim gradients (HOS error or fault, i.e. higher order shimming). For reset:

  • Enter on the computer: "permproc stop scanner"
  • Turn off the 3 switches (at the bottom) of the shim gradients in the technical room. Turn off in following order: Middle, Right, Left and wait a couple of seconds
  • Turn on the 3 switches in reversed order
  • Enter on the computer: "permproc start scanner"

Airflow in magnet bore is insufficient (typically after bi-monthly emergency power test)

Caused by the building's climate control system not rebooting, resulting in too limited airflow to the scanners. Call 88, describe the problem!

gradients overheating

For certain protocols, the gradients may approach their critical temperature (65 degrees). When this happens, the scan will abort and you will have to wait until the gradients have cooled down completely (~30 minutes). To avoid this, you can switch on the multimeter on the desk (set to Volt) and monitor the temperature while you scan. The reported value is temperature in degrees C/10. E.g. 5.5 means the gradients are at 55 degrees.

Power off and power on sequence(s)

CDAS

  • exit scanner application software
  • stop all processes/services: start_stop_procs.pl stop (easier than shutting down host)
  • Reset CDAS: turn off green switch. Wait 5 seconds.
  • Turn red switch.
  • Unplug sense-cable (on top, labeled with red arrow, this will reset/enable bore light). Wait 5 seconds.
  • Turn on in reverse order: red switch and green switch.
  • Wait for bed-lights (top) to turn green. Now plug in the sense-cable (red arrow). This controls bore light.
  • At bed console, set light to 50%.
  • start all processes/services: start_stop_procs.pl start
  • wait, then start application software

Main System

Compressors

Procedure testing/resetting compressors Helium pump: 2 small cubic devices in the far right corner. The green light on the left device should be flashing. Check messages on small LED-displays: scroll with arrow up/down buttons. Should all be OK, not ERR. Temperature of tubes should be below room temperature (i.e. cold). To reset: press OFF. You should hear it switching off. Wait, and press ON, again hearing it switching on. To hard reset: Press OFF. Wait. Turn small black switch from I to O. Wait. Turn back to I. Wait. Important: press ON to turn the compressor back on.

Patient ventilation system

Box hanging the CDAS rack. Turn off by unplugging 220V cable.

Coil-specific tips 'n tricks

Microcoils MR Coils (surface coils)

  • acquire B0 not with commonly used pickup coil elements but instead the surface coil elements. The Shimtool should apply mask to area with signal only
  • connect the two surface coils mixed on the two interface boxes, not one separately on each box

BOLD screen

Turn on by switching the switch in the console room to ON. Turn off after use! The visibility range in the vertical direction is from -4 to +3 on the desktop image. This means that at the top ~10% of the screen cannot be used.

Contact information

Philips contacts

Anton Heijmans: 06 22491918 Maarten Versluis: 06 11386561 Philips service: 040 7001210

AMC Contacts

During office hours, contact front office on phone number 88, option 2 Regelkamer: 62900 (outside office hours) Ed de Klerk: 06-30005770 Tom Emke: 020-5662305, 06-22452389 Roelofsen: 68103

QA

QA has moved here: 7T MRI Quality assurance*