Archive - Revision history

Yingzhu at 23:49, 20 January 2021

2021-01-20T23:49:46Z

Yingzhu at 22:20, 20 January 2021

2021-01-20T22:20:10Z

Yingzhu at 22:14, 22 December 2020

2020-12-22T22:14:59Z

← Older revision		Revision as of 22:14, 22 December 2020
Line 2:		Line 2:


	=~~How To Section 1 - Micro-CT Scanning=~~		=SkyScan Micro-CT Scanning=


	==Micro-CT Scanning==

	~~===Scanco Setting Possibilites===~~
	~~:E (kVp): 50, 60 70~~

	~~:I (uA): 80, 160~~

	~~:Integration time (ms): 100, 200, 350~~

	===Settings Suggestions for SkyScan bone scanning===		===Settings Suggestions for SkyScan bone scanning===
Line 1,029:		Line 1,019:
	[[Howto_3\| Sample COM Files]]		[[Howto_3\| Sample COM Files]]


	~~==Scanco AIM File Format==~~

	*(this section has been uploaded as a Word document. Click the link below.)

	~~:[[Media:Scanco_Aim_File_Format.doc\| Scanco Aim File Format Document]]~~

	==Sample COM Files==		==Sample COM Files==
Line 2,476:		Line 2,460:


	=SAP ~~realted~~=		=SAP related=

	==Fix SAP colours when green==		==Fix SAP colours when green==

Yingzhu at 19:39, 22 December 2020

2020-12-22T19:39:44Z

Show changes

Skboyd: /* Corrections for Ring Artifacts and Filter Use */

2009-11-16T22:44:58Z

Corrections for Ring Artifacts and Filter Use

← Older revision		Revision as of 22:44, 16 November 2009
Line 37:		Line 37:
	''email, forwarded from Alexander Sasov, sasov@skyscan.be''		''email, forwarded from Alexander Sasov, sasov@skyscan.be''
	# <U>If ring artifacts appear only when you scan with a filter, you should acquire new flat-field reference for that particular filter and save it. Possible reasons for the rings are switching to another voltage or current or exposure, some particles in the filter surface, cracks or just small changes in the x-ray spectrum of the source, which normally appear in several years of usage.</U>		# <U>If ring artifacts appear only when you scan with a filter, you should acquire new flat-field reference for that particular filter and save it. Possible reasons for the rings are switching to another voltage or current or exposure, some particles in the filter surface, cracks or just small changes in the x-ray spectrum of the source, which normally appear in several years of usage.</U>
	# Normally one should acquire new flat-field references ~~twice~~ per year or in the case of the appearance of strong ring artifacts. Another reason to acquire new flat-field references is a system operation with new voltage/current/exposure. Don't forget to save new flat-field references directly after acquisition.		# Normally one should acquire new flat-field references t wice per year or in the case of the appearance of strong ring artifacts. Another reason to acquire new flat-field references is a system operation with new voltage/current/exposure. Don't forget to save new flat-field references directly after acquisition.

	===Specimen Holders===		===Specimen Holders===

Skboyd: /* Add a project to vtkMy */

2006-05-24T18:39:21Z

Add a project to vtkMy

← Older revision		Revision as of 18:39, 24 May 2006
Line 1,723:		Line 1,723:
	# Run CMake, taking the source code from vtkMy/src and building the binaries in vtkMy/bin.		# Run CMake, taking the source code from vtkMy/src and building the binaries in vtkMy/bin.
	# Open the Visual C++ workspace and edit the source code (since at the moment it will be a duplicate of whatever project you copied in step 3).		# Open the Visual C++ workspace and edit the source code (since at the moment it will be a duplicate of whatever project you copied in step 3).
	# Compile your new code. Usually, all the development should be done in the ? mode (rather than ?, etc.).		# Compile your new code. Usually, all the development should be done in the “Debug�? mode (rather than “Release�?, etc.).
	# If, to run your application, you need to include command line arguments, go to the menu item [Project][Settings], and on the ‘debug’ tab set the Program Arguments as shown.		# If, to run your application, you need to include command line arguments, go to the menu item [Project][Settings], and on the ‘debug’ tab set the Program Arguments as shown.

Skboyd: /* HowTo: Requeue a process */

2005-11-03T19:07:59Z

HowTo: Requeue a process

← Older revision		Revision as of 19:07, 3 November 2005
Line 971:		Line 971:


	~~===HowTo: Requeue a process===~~

	~~:* Find the process identification using <code>see</code>~~
	~~:* The process must be <I>pending</I>, not <I>processing</I>!~~
	~~:* <code>set entry 1131 /requeue=BLUND_LARGE </code>(this is a seldom used queue, good for quick things).~~

Skboyd: /* Setting up CVS access from Linux/Unix */

2005-09-07T14:06:58Z

Setting up CVS access from Linux/Unix

← Older revision		Revision as of 14:06, 7 September 2005
Line 1,806:		Line 1,806:
	<U>NOTES ABOUT KEYS</U>		<U>NOTES ABOUT KEYS</U>
	Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,		Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
	and the "id_rsa" is the private key.		and the "id_rsa" is the private key.
	Every user on every computer should only have ONE "id_rsa" file,		Every user on every computer should only have ONE "id_rsa" file,
	but can have multiple "id_rsa.pub" files concatenated into		but can have multiple "id_rsa.pub" files concatenated into
	their "authorized_keys" file.		their "authorized_keys" file.

	===Using CVS from a command line===		===Using CVS from a command line===

Skboyd: /* Setting up CVS access from Linux/Unix */

2005-09-07T14:06:34Z

Setting up CVS access from Linux/Unix

← Older revision		Revision as of 14:06, 7 September 2005
Line 1,806:		Line 1,806:
	<U>NOTES ABOUT KEYS</U>		<U>NOTES ABOUT KEYS</U>
	Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,		Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
	and the "id_rsa" is the private key.		and the "id_rsa" is the private key.
	Every user on every computer should only have ONE "id_rsa" file,		Every user on every computer should only have ONE "id_rsa" file,
	but can have multiple "id_rsa.pub" files concatenated into		but can have multiple "id_rsa.pub" files concatenated into
	their "authorized_keys" file.		their "authorized_keys" file.

	===Using CVS from a command line===		===Using CVS from a command line===

Skboyd: /* Setting up CVS access from Linux/Unix */

2005-09-07T14:06:11Z

Setting up CVS access from Linux/Unix

← Older revision		Revision as of 14:06, 7 September 2005
Line 1,805:		Line 1,805:

	<U>NOTES ABOUT KEYS</U>		<U>NOTES ABOUT KEYS</U>
	Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys, and the "id_rsa" is the private key.		Remember, the "authorized_keys" file is a concatenation of public (id_rsa.pub) keys,
	Every user on every computer should only have ONE "id_rsa" file, but can have multiple "id_rsa.pub" files concatenated into		and the "id_rsa" is the private key.
			Every user on every computer should only have ONE "id_rsa" file,
			but can have multiple "id_rsa.pub" files concatenated into
	their "authorized_keys" file.		their "authorized_keys" file.