Agilent

Last-modified: 2023-07-16 (Sun) 05:13:22 (287d)

FrontPage

Schedule

  • He filling(2011.May.?)
  • Console upgrade (2011.Mar, to be fixed)
  • Half year maintenance(?)
  • Annual report(PDFs and data from new console)
  • VNMRJ3 release schedule

Information

Stuffs & construction

  • Receiver board spare
  • Gradient AMP module x 2 (2010.Aug Mr.Seki promised)
  • Gradient Temperature sensor problem(Low impedance cable)
  • Error announcement system for coldhead, air conditioner and so on
  • Interphone in bay room
  • DECC board spare(Did we get? Need confirm)

Problem

  • DSP buffer overwrite error
    • [uken:sperry]~> /sbin/ifconfig -a eth1
        eth1      Link encap:Ethernet  HWaddr B8:AC:6F:8E:A0:26  
                  inet addr:10.0.0.1  Bcast:10.0.0.255  Mask:255.255.255.0
                  inet6 addr: fe80::baac:6fff:fe8e:a026/64 Scope:Link
                  UP BROADCAST MULTICAST  MTU:1500  Metric:1
                  RX packets:83765980 errors:0 dropped:5 overruns:0 frame:280
                  TX packets:8813798 errors:0 dropped:0 overruns:0 carrier:0
                  collisions:0 txqueuelen:1000 
                  RX bytes:111694971422 (104.0 GiB)  TX bytes:5696192732 (5.3 GiB)
                  Interrupt:177 Memory:f4be0000-f4bf0000 
        Network switches were replaced(Apr.19.2012 by Mr.Tajika)

To be asked

  • Infrared light bulbs

Other issues

  • second Oil attenuator(30dB)
  • Old gradient coil
  • Pulse oxymeter update
  • Color printer for printing screen
  • UPS
  • Patient table controller

Completed

  • Air conditioner replace(2011.Apr.15)
  • He filling & Ramp-down(2011.Feb.28)
  • Window replace for shield room(2011.Mar)
  • Shield performance improve
  • Solution for /usr4 saving problem (Kuribayashi)
    • No answer but we won't have this problem in future
  • Modification of joints for ethylene glycol circuit(Grad Amp cooler)

Question about the new console & vnmrj

  • How to make customization on the shimming interface(buttons and value input box).
    • He doesn't know.
  • How to control the cmdHistory feature. It seems the current history length is set to be 100 items. How can we increase the number(e.g. 10000 items)? (~/vnmrsys/cmdHistory is always empty is there any function? What is persistence/CmdHistoryMenu? vnmrsys/persistence/CommandHistory is having up to 100 recent commands.)
    • Allen may have asked and got some reply already.
  • Is there any way to make experimental package(shim,scout,epi,3d,etc) and retrieve them at a same time ?
  • How can we confirm the current threshold setting set by chartstrip? And we want really confirm the system is really monitoring the RF or not.(System can run without chartstrip running)
    • He doesn't know.
  • After RF safety monitor tripping, we run "su acqproc" twice then start "chartstrip" again. Is this must-procedure or is there any simpler way to make it?
    • He doesn't know.
  • After finishing acquisition, output trigger port stays(sp1~3) as the status set during the acquisition. We want to reset(set them to zero) at the end of the acquisition(interrupted end as well). How does Agilent suggest to achieve this?
    • Allen may have asked and got some reply already.
  • Is there anyway to confirm the error indicator status from the DELL machine?
    • He doesn't know.
  • VNMRJ says 'sa' command is not supported. Why? Any other way to stop experiment and store the data safely?
    • 'sa' command was terminated. No replacement. The stopped experiment by 'aa' cannot be resumed again.
  • When we toggle the tab to Start>Prescan RCVRS setting is automatically changed to the setting indicated by coil_param[19] value. Why? How can we avoid the automated feature?
    • He doesn't know. He'll check.
  • To convert data to nifti, fdf2nifti(vnmrj3) command may be available. Any instruction for it? Is there any way to put correct nifti coordinate info into the nifti file?
    • He doesn't know.
  • Single shot GE image taken by gems and gemsir are very different. gemsir gives stripe artifacts. Why?
    • He did know about the artifact and made the modified gemsir sequence(gemsir_N_seg.c). It has slice non-selective inversion pulse(hard). The gradient timing may be also the issue.

  • How to use adiabatic pulses for the inversion. How to avoid the automated power calculation not to have an error.
    • put '-1' in the flip angle text box, then the automatic calculation won't be done.
  • Any editable bootup/shutdown script for vnmrj?
    • "exit" macro can be used. He'll check later.
  • How we can get individual coil 3D images?
    • He'll check.
  • How to make fdf images from individual coils.
    • We can choose the images displayed in vnmrj and save them.
  • How to use "tabc" command as unix command line tool.
    • He doesn't know.
  • When we use our petable file for mprage, the acquired data cannot be shown properly and vnmrj is frozen(need to close vnmrj to recover). The study queue is displayed with green color(It says "Executing..") Why?
    • 3D sequence's recon program hate any other information than t1. Our t3 parameter and comment lines are the source of the problem.
  • "file: ~/vnmrsys/exp1/datadir3d/data/data.fdf does not exist" error for mprage3d with petable(256lin4k)
    • This may be caused by the same problem as described above.
  • Any way to copy t1(petable) data to other parameter and keep the information to procpar file(pelist parameter may be good for it)
    • Impossible. We may need to think about how to make it with him.
  • gradient system timing correction
    He measured the timing lag of our gradient system. It was 60 micro sec. When the value is written in our gradtable file, pulse sequence can take care for the lag. [ grad_advance(gpropdelay) is the code for it ]  Now we only have single value which is applied for 3 gradient system equally but vnmrj3 will take 3 values for 3 gradient axis. We need to measure them again. 
  • Commens by Mr.Kuribayashi:
    RF spoiling is recommended to be used.

Nova issue

  • We are having 4 spectrum peaks when we set rcvrs='yyyy' and rcvcoil='volume'
    • It seems array coils are not detuned well(or at all) when we set volume receive mode. It may be the reason why we can observe the rf signals from ch2,3,4 even when the receiver mode is volume receive. Can it be just a feature?