A husband visited a marriage counselor and said, "When we were first married, I would come home from the office, my wife would bring my slippers and our cute little dog would run around barking. Now after ten years, it's all different. I come home, the dog brings the slippers and my wife runs around barking."
"Why complain?" said the counselor, "You're still getting the same service."
[Author: unknown]
Thursday, February 10, 2011
Saturday, June 28, 2008
/var/log/messages snippet
Jun 29 11:30:29 ida NetworkManager: starting...
Jun 29 11:30:29 ida NetworkManager: eth0: Device is fully-supported using driver 'e100'.
Jun 29 11:30:29 ida NetworkManager: Found new Ethernet device 'eth0'.
Jun 29 11:30:29 ida NetworkManager: (eth0): exported as /org/freedesktop/Hal/devices/net_00_11_11_5f_f0_52
Jun 29 11:30:29 ida NetworkManager: Trying to start the supplicant...
Jun 29 11:30:29 ida NetworkManager: Trying to start the system settings daemon...
Jun 29 11:30:30 ida kernel: Loading iSCSI transport class v2.0-869.
Jun 29 11:30:30 ida nm-system-settings: Loaded plugin ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jun 29 11:30:30 ida kernel: iscsi: registered transport (tcp)
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-br0 ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: error: Unknown connection type 'Bridge'
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: read connection 'System eth0'
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: error: Ignoring loopback device config.
Jun 29 11:30:31 ida kernel: iscsi: registered transport (iser)
Jun 29 11:30:31 ida iscsid: iSCSI logger with pid=1966 started!
Jun 29 11:30:32 ida iscsid: transport class version 2.0-869. iscsid version 2.0-868
Jun 29 11:30:32 ida iscsid: iSCSI daemon with pid=1967 started!
Jun 29 11:30:33 ida NetworkManager: (eth0): device state change: 1 -> 2
Jun 29 11:30:33 ida NetworkManager: (eth0): bringing up device.
Jun 29 11:30:33 ida kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Jun 29 11:30:33 ida kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 29 11:30:33 ida kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 29 11:30:33 ida NetworkManager: (eth0): preparing device.
Jun 29 11:30:33 ida NetworkManager: (eth0): deactivating device.
Jun 29 11:30:33 ida NetworkManager: (eth0): carrier now ON (device state 2)
Jun 29 11:30:33 ida NetworkManager: (eth0): device state change: 2 -> 3
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) starting connection 'System eth0'
Jun 29 11:30:33 ida NetworkManager: (eth0): device state change: 3 -> 4
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Jun 29 11:30:33 ida NetworkManager: (eth0): device state change: 4 -> 5
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 29 11:30:33 ida NetworkManager: (eth0): device state change: 5 -> 7
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) started...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled...
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 4 of 5 (IP Configure Get) complete.
Jun 29 11:30:33 ida NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) started...
Jun 29 11:30:33 ida NetworkManager: nm_utils_ip4_netmask_to_prefix: assertion `ip4_netmask != 0' failed
Jun 29 11:30:34 ida NetworkManager: (eth0): device state change: 7 -> 8
Jun 29 11:30:34 ida NetworkManager: nm_system_device_replace_default_ip4_route(): rtnl_route_add() returned error Unknown error 4294967293 (-3)#012Sucess#012
Jun 29 11:30:37 ida NetworkManager: Policy set (eth0) as default device for routing and DNS.
Jun 29 11:30:37 ida NetworkManager: Activation (eth0) successful, device activated.
Jun 29 11:30:37 ida NetworkManager: Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete.
Jun 29 11:30:37 ida kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Jun 29 11:30:37 ida nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/05-netfs' exited with error status 1.
Jun 29 11:30:29 ida NetworkManager:
Jun 29 11:30:29 ida NetworkManager:
Jun 29 11:30:29 ida NetworkManager:
Jun 29 11:30:29 ida NetworkManager:
Jun 29 11:30:29 ida NetworkManager:
Jun 29 11:30:30 ida kernel: Loading iSCSI transport class v2.0-869.
Jun 29 11:30:30 ida nm-system-settings: Loaded plugin ifcfg-fedora: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Jun 29 11:30:30 ida kernel: iscsi: registered transport (tcp)
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-br0 ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: error: Unknown connection type 'Bridge'
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-eth0 ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: read connection 'System eth0'
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: parsing /etc/sysconfig/network-scripts/ifcfg-lo ...
Jun 29 11:30:31 ida nm-system-settings: ifcfg-fedora: error: Ignoring loopback device config.
Jun 29 11:30:31 ida kernel: iscsi: registered transport (iser)
Jun 29 11:30:31 ida iscsid: iSCSI logger with pid=1966 started!
Jun 29 11:30:32 ida iscsid: transport class version 2.0-869. iscsid version 2.0-868
Jun 29 11:30:32 ida iscsid: iSCSI daemon with pid=1967 started!
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida kernel: e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Jun 29 11:30:33 ida kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun 29 11:30:33 ida kernel: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager:
Jun 29 11:30:33 ida NetworkManager: nm_utils_ip4_netmask_to_prefix: assertion `ip4_netmask != 0' failed
Jun 29 11:30:34 ida NetworkManager:
Jun 29 11:30:34 ida NetworkManager:
Jun 29 11:30:37 ida NetworkManager:
Jun 29 11:30:37 ida NetworkManager:
Jun 29 11:30:37 ida NetworkManager:
Jun 29 11:30:37 ida kernel: vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
Jun 29 11:30:37 ida nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/05-netfs' exited with error status 1.
Sunday, February 18, 2007
Spatial sorting of (DICOM) 2D slices in 3D space.
3D position info (in the slice's header) cannot be used because otherwise, as you can very well see, the slices toward the 'End' will get mixed up with those in the 'Middle'!
Wednesday, February 14, 2007
Jaggies problem.
There are 3 screenshots. In each, the left one is mine, the right one is from OsiriX (a VTK-based application for Mac OS X).
Figure 1. This is the comparison of one of the 23 original 2D slices. Note that when displaying the original slice, there's virtually no quality issue at all!
I build a 3D volume from these 23 slices by repeating each slice's pixels in real-world 3D space till the (voxel) plane thickness becomes equal to the thickness reported in the slice's file header.
Figure 2. This is the coronal transverse section of the volume.
Figure 3. This is the sagittal transverse section of the volume.
My guess is, if there were let's say 1000 such slices (to be displayed in a 512x512 pixel view), the jaggies problem wouldn't manifest... probably because of going from high-resolution data (1000 lines) to low resolution (512 lines).
Figure 1. This is the comparison of one of the 23 original 2D slices. Note that when displaying the original slice, there's virtually no quality issue at all!
I build a 3D volume from these 23 slices by repeating each slice's pixels in real-world 3D space till the (voxel) plane thickness becomes equal to the thickness reported in the slice's file header.
Figure 2. This is the coronal transverse section of the volume.
Figure 3. This is the sagittal transverse section of the volume.
My guess is, if there were let's say 1000 such slices (to be displayed in a 512x512 pixel view), the jaggies problem wouldn't manifest... probably because of going from high-resolution data (1000 lines) to low resolution (512 lines).
Subscribe to:
Posts (Atom)