text:
this use is very old, cp. Glúm. ch. 26, Grág. Þ. Þ. ch. 56, Edda 103, Bs. i. 450, the Sagas and laws passim; hence fardaga-helgi, f. the Sunday in fardagar, Grág. ii. 12; fardaga-leiti and fardaga-skeið, n. the time of fardagar, Ísl. ii. 26.
FARÐI, a, m. [Fr. fard; Old Engl. fard. farding; Norse fare, Ivar Aasen], scum (in milk, curds), and farða, að, to have scum formed on it.
far-drengr, m. a sea-faring man, Edda 107, Fms. ii. 23, Þorf. Karl. 402.
far-flótti, adj. fugitive, exiled, Hkr. i. 252: with gen., Fas. iii. 103.
far-fúss, adj. eager for departing, Bs. ii. 35, 130.
far-fýsi, f. eagerness to depart or travel, Fms. iii. 45, Fs. 46.
FARG, n. [cp. Ulf. fairguni--a mountain], a press, press-weight; vera undir fargi, to be under a press, Bjarni 132.
farga, að, I. with acc. to press, Hom. 152, Bs. ii. 118. II. with dat. to destroy, make away with, Bb. 1. 7.
farga, u, f. [for. word, cp. farga. Du Cange], a sort of stuff, Pm. 6.
far-gögn, n. pl. luggage, Nj. 266: sing., Stj. 367.
far-görvi, n. travelling gear, Eg. 727, Edda 110.
fari, m. a sea-farer, in compds, Dyflinnar-fari, a Dublin trader; Englands-fari, an English seaman, Baut. 387, Rafn 217, Fms. vi. 240; Hlymreks-fari, a Limerick seaman, Landn.; Hallands-fari; Hólmgards-fari, one who trades to Holmgard; Jórsala-fari (a traveller to Jerusalem). Fms., Ann.
far-kona, u, f. a beggar-woman, Sturl. ii. 108. farkonu-sótt, f., medic. erysipelas (?), Ann. 1240.
far-kostr, m. [Swed.-Norse farkost; Scot. farcost], a ferry-boat, a ship, Fms. vi. 219, Edda 48, Grág. ii. 130, Fb. i. 546, Ver. 8, Thom. 29.
far-lami, adj. lame and unable to go, Bs. i. 303.
far-land, n., poët. the land of ships, the sea, Lex. Poët., cp. Og. 31.
far-leiga, u, f. passage-money, Gþl. 415.
far-lengd, f. travels, journey, Bs. i. 450, 758. Fms. v. 273. Thom. 173.
far-ligr, adj. comfortable: farlig sæng, a soft bed, Vellekla.
far-ljós, f. adj. light enough for travelling, of the night, Eg. 88, Fbr. 97 new Ed.
far-lög, n. pl. nautical law, Grág. ii. 399.
far-maðr, m. a seaman, sea-faring man, Landn. 180, Bs. i. 66, Nj. 61, Eg. 154, Fms. i. 11, iv. 124, 174. Þorst. hv. 44, Grág. i. 190. COMPDS: farmanna-búðir, f. pl. merchant booths. K. Þ. K. 34. farmanna-lög, n. pl. = farlög, Jb. 7.
far-móðr, adj. weary from travelling, Fms. ix. 233, v. 288.
FARMR, m. a fare, freight, cargo, Jb. 411, Eg. 129, Band. 5, Fms. iv. 259, Grág. ii. 395: metaph. a load in general, vide Lex. Poët.: in the Edda, Odin is Farma-guð and Farma-týr, m. the god and helper of loads,--he also was invoked bv sailors; skips-f., a ship's freight: viðar-f., timbr-f., korn-f., hey-f., etc., a load of wood, timber, corn, hay, etc.
farnaðr and förnuðr, m., gen. ar, furtherance, speed; tíl farnaðar mér ok til ferðar, Grág. ii. 21, Skv. 1. 8, Fms, viii. 31; ú-farnaðr, bad speed; þar til hon kynni sér f., till she knew how to speed in the world, Ld. 116.
far-nagli, a, m. the water-peg in a ship's bottom, in mod. usage negla, Edda (Gl.); cp. var-nagli.
farnask, að, dep. to speed well, Fms. iv. 56.
far-nest, n. viands. Eb. 196, Skálda 173.
farning, f. a ferrying over, passage; veita e-m f., Pd. 16, K. Þ. K. 24, Glúm. 371, Fbr. 158, Sturl. i. 18. Ísl. ii. 386, Grág. i. 98.
far-rek, n. shipwreck, in a metaph. sense; þat hafði Þórði orðit til farreks, at hestar hans báðir vóru í brottu, i.e. Th. was wrecked, in that he had lost both his ponies, Ísl. ii. 318; skulu vér frændr þínir veita þér styrk til þess at þú komir aldri síðan í slíkt f., in such a strait, Fms. iv. 270.
FARRI, a, m. [A. S. fearr; Germ. farre = a bullock], a bullock, Ýt. 14, Edda (Gl.) β. [farri, Ivar Aasen], a landlouper, vagrant, Clar. (Fr.) COMPD: farra-fleinn, m. prop. a landlouper; Alm. 5 spells fjarra-fleinn, N. G. L. ii. 154, v.l. fira-fleinn, both wrongly as it seems, cp. farra-trjóna, f. 'bullock-snout,' Ýt. l.c., cp. also Germ. farren-schwanz and farren-kope (Grimm); the verse in Alm. 5 is probably addressed to the dwarf, not (as in the Edd.) the dwarf's own words.
far-serkr, m. travelling sark or jacket, a nickname, Landn.
far-skip, n. a ferry-boat, Gþl. 416.
far-snilli, f. nautical art, Fb. iii. 385.
far-sumar, n. the season for sea-faring, Ann.
far-synjan, f. refusing to ferry one, Hbl. 59.
far-sæla, u, f., prop. good speed (in travelling); but only used metaph. good speed, prosperity, happiness, freq. in that use, esp. in eccl. sense, 623. 52. Stj. 327; f. þessa heims, Hom. 29, 76. Fms. i. 104, vi. 155, x. 276, 409.
far-sælask, d, dep. to speed, have luck, Fs. 34.
far-sæld, f. = farsæla; friðr ok f., peace and happiness, Fms. xi. 438, Barl. 62: in pl., 655 xxxii. 9; ó-farsæld, misfortune.
far-sæll, adj. speeding well in voyages; svá f. at hann kaus sér jafnan höfn, Korm. 140; þat er mælt at þú sért maðr farsælli en aðrir menn flestir, Fb. iii. 385: farsælli en aðrir menn, Band. 5, Barl. 195: of a ship, farsælla en hvert annarra, Fs. 27 (obsolete). 2. metaph. prosperous, very freq., esp. in eccl. sense: ó-farsæll, unhappy.
far-sælligr, adj. (-liga, adv.), prosperous. Fms. ii. 36, v. 37.
far-tálmi, a, m. hinderance in one's journey, Gþl. 417, Al. 61.
far-tekja, u, f. taking a passage in a ship, Jb. 377, N. G. L. i. 58.
far-vegr, m. a track, Fms. v. 225, ix. 366, xi. 316; manna f., a track of men, Gþl. 538, Stj. 71: metaph., Sks. 565 B. 2. a 'fair way,' a channel, bed of a river, Landn. 65, Grág. ii. 281, Stj. 230, Fms. iv. 360 (freq.) 3. a road, journey; langr f., Fms. xi. 16, v. 225.
far-viðr, m. [farvid, Ivar Aasen], faggots, Björn.
far-þegi, a, m. [þiggja], a passenger, Finnb. 278, Ann. 1425, Ld. 86, 112, Bs. ii. 47, Fas. ii. 171.
FAS, n. gait, bearing; Icel. say, vera hægr, stilltr í fasi, or fas-góðr, fas-prúðr, adj. of gentle gait and bearing; fas-mikill, adj. rushing: this word, though in freq. use at the present time, seems never to occur in old writers, unless it be in arga-fas, q.v.: the etymology is uncertain, perhaps from Engl. fashion, face; it seems at all events to be of foreign origin; at the time of Pal Vídalín it was in full use, cp. Skýr. 90.
fasi, a, m. a nickname, Fms. x. 27.
FASTA, u, f. [Ulf. fastubni; O. H. G. fastá; Germ. faste; Swed. fasta; Dan. faste; a word introduced along with Christianity; the old Scandinavians could have no such word, as voluntary fasting was unknown in the heathen rites, and at the first introduction of Christianity the practice was sorely complained of, cp. Hkr. Hák. S. Góða, ch. 17] :-- a fast, fasting, Hom. 73, K. Þ. K. 122, Rb. 82; the word therefore occurs first in poets of the beginning of the 11th century, e.g. Fms. vi. 86, cp. boð-f., lög-f., etc. COMPDS: föstu-afbrigð, f. breaking the fast, K. Á. 192. föstu-bindandi, f. abstinence in fasting, Stj. 147. föstu-dagr, m. a fast-day, K. Á. 186, 187, Nj. 165; the Icel. name of Friday, Rb. 112, Grág. i. 146; Föstudagr Langi, Good Friday, Nj. 158. Föstudags-nótt, f. Friday night, K. Þ. K. 122. Föstu-kveld, n. Friday evening, Fms. vii. 159, Nj. 187. föstu-matr, m. fast-day food, Sturl. i. 139, Fms. iv. 283, v.l. Föstu-morgin, m. Friday morning, Orkn. 370. Föstu-nátt, f. Friday night, Nj. 186: fast-nights, K. Þ. K. 122. föstu-tíð, f. fast-time, Fms. v. 199, K. Þ. K. 134, Am. 37. föstu-tími, a, m. fast-time, Stj. 148. II. Lent, Fms. viii. 28, Ld. 320, N. G. L. i. 12; distinction is made between the Easter Lent, (sjö-vikna Fasta, seven weeks Lent, also called langa F., the long Fast, K. Þ. K. 122, Bs. i. 801, and passim; níu-vikna F., the nine weeks Lent, K. Þ. K. 122, Grág. i. 325), and Jóla-f., (the Yule Lent, the time from Advent to Yule, Grág. l.c., Rb. 46, K. Þ. K. 124.) Föstu-gangr or Föstu-ígangr and -inngangr, m. beginning of these seasons, esp. Lent; fimm eru föstu-ígangar, Clem. 58, Sturl. iii. 81, Rb. 4 (v.l.), 48, 76. Föstu-prédikan, f. a Lenten sermon. Föstu-tjald, n. hangings used in churches during Lent, Vm. 52, 109.
fasta, að, to fast: 1. eccl., Hom. 71, 73, Ld. 200, K. Á. 160, Bs. passim, Fms. ii. 250, N. G. L. i. 141, 144. 2. secular; af fastanda manns munni, Sks. 450, Lækn. 471.
fasta, adv. = fastlega, Lex. Poët.
fasta-eign, mod. fast-eign, f. landed property, Stj. 224, H. E. ii. 85, 223.
fasta-far, n., í fastafari, eagerly, Th. 76, Stj. 287, 291.
fasta-land, n. the mainland (Germ. festes land), opp. to ey-land.
fast-aldi, a, m. a cognom., Landn., prop. of a bear.
fastendi (fastyndi), n. pl. surety, N. G. L. i. 449, H. E. i. 247.
fast-eygr, adj. firm-eyed, Sturl. ii. 133, Bs. i. 127.
fast-garðr, m. a fastness, stronghold, Fas. i. 266.
fast-haldr, adj. fast-holding, tenacious, saving, Fms. x. 409. β. as subst. a key, Edda (Gl.): a shackle, Fastaldr var á Fenri lagðr, Mkv.
fast-heitinn, adj. true to one's word, Sturl. iii. 122.
fast-heldi, f. tenacity, perseverance, Stj. 155, Fb. ii. 14.
fast-hendr, adj. close-fisted, Sks. 440.
FASTI, a, m., poët. fire, Lex. Poët., root uncertain: the phrase, færa e-n í fasta, to bring one into a strait, 'between two fires,' Þd.
fast-liga, adv. firmly, strongly, Sks. 374. β. metaph., Hom. 114, Fms. v. 217, Fas. i. 4; trúa f., to believe firmly, Fms. v. 242; bjóða f., Stj. 54: e-t horfir f., it looks hard, unyielding, difficult, Lv. 94; vera f. kominn, to be fast shut up, Eg. 519, Ld. 52.
fast-ligr, adj. fast, firm, strong, Stj. 26, Sturl. iii. 140, Bs. i. 517.
fast-lyndr, adj. strong-minded, Finnb. 210.
fast-mæli, n. a fast engagement, Fms. i. 206, iii. 85, vii. 164, Bjarn. 58.
fastna, að, to pledge; f. lögbót, K. Þ. K. 24. β. esp. to betroth, to give the bride away at the betrothal, Grág. i. 302 sqq.; fastnaði Mörðr Rúti dóttur sína, Nj. 3, 51, Band. 3, Ísl. ii. 8, 163, 206, Ld. 22. γ. reflex. to be betrothed, given awav. Fms. x. 284.
fastnaðr, m. betrothal, H. E. i. 246, 247; vide festar.
fastnandi, part. a betrother, one who gives a bride away, Grág. i. 305.
fast-næmr, adj. fast, firm, trusty, Dropl. 6, Valla L. 208, Fs. 13.
fast-ofinn, part. stout, of stuff, Lex. Poët.
fast-orðr, adj. true to one's word, Fms. vi. 52, vii. 120.

matches: v. v. v. v. v. v. v. v.


text:
AggregateState An instance of AggregateState is used in aggregate method invocations as specified by the XL programming language.
BooleanAggregateState BooleanAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type boolean.
BooleanConsumer BooleanConsumer is a callback interface.
BooleanFilterState BooleanFilterState is the subinterface of FilterState that is used for filter methods with return value of type boolean.
BooleanToBoolean Instances of BooleanToBoolean represent functions which take booleans as input and return values of type boolean.
BooleanToBooleanGenerator Instances of BooleanToBooleanGenerator represent generator functions which take booleans as input and yield sequences of values of type boolean.
BooleanToByte Instances of BooleanToByte represent functions which take booleans as input and return values of type byte.
BooleanToByteGenerator Instances of BooleanToByteGenerator represent generator functions which take booleans as input and yield sequences of values of type byte.
BooleanToChar Instances of BooleanToChar represent functions which take booleans as input and return values of type char.
BooleanToCharGenerator Instances of BooleanToCharGenerator represent generator functions which take booleans as input and yield sequences of values of type char.
BooleanToDouble Instances of BooleanToDouble represent functions which take booleans as input and return values of type double.
BooleanToDoubleGenerator Instances of BooleanToDoubleGenerator represent generator functions which take booleans as input and yield sequences of values of type double.
BooleanToFloat Instances of BooleanToFloat represent functions which take booleans as input and return values of type float.
BooleanToFloatGenerator Instances of BooleanToFloatGenerator represent generator functions which take booleans as input and yield sequences of values of type float.
BooleanToInt Instances of BooleanToInt represent functions which take booleans as input and return values of type int.
BooleanToIntGenerator Instances of BooleanToIntGenerator represent generator functions which take booleans as input and yield sequences of values of type int.
BooleanToLong Instances of BooleanToLong represent functions which take booleans as input and return values of type long.
BooleanToLongGenerator Instances of BooleanToLongGenerator represent generator functions which take booleans as input and yield sequences of values of type long.
BooleanToObject<V> Instances of BooleanToObject represent functions which take booleans as input and return values of type V.
BooleanToObjectGenerator<V> Instances of BooleanToObjectGenerator represent generator functions which take booleans as input and yield sequences of values of type V.
BooleanToShort Instances of BooleanToShort represent functions which take booleans as input and return values of type short.
BooleanToShortGenerator Instances of BooleanToShortGenerator represent generator functions which take booleans as input and yield sequences of values of type short.
BooleanToVoid Instances of BooleanToVoid represent functions which take booleans as input and return values of type void.
BooleanToVoidGenerator Instances of BooleanToVoidGenerator represent generator functions which take booleans as input and yield sequences of values of type void.
ByteAggregateState ByteAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type byte.
ByteConsumer ByteConsumer is a callback interface.
ByteFilterState ByteFilterState is the subinterface of FilterState that is used for filter methods with return value of type byte.
ByteToBoolean Instances of ByteToBoolean represent functions which take bytes as input and return values of type boolean.
ByteToBooleanGenerator Instances of ByteToBooleanGenerator represent generator functions which take bytes as input and yield sequences of values of type boolean.
ByteToByte Instances of ByteToByte represent functions which take bytes as input and return values of type byte.
ByteToByteGenerator Instances of ByteToByteGenerator represent generator functions which take bytes as input and yield sequences of values of type byte.
ByteToChar Instances of ByteToChar represent functions which take bytes as input and return values of type char.
ByteToCharGenerator Instances of ByteToCharGenerator represent generator functions which take bytes as input and yield sequences of values of type char.
ByteToDouble Instances of ByteToDouble represent functions which take bytes as input and return values of type double.
ByteToDoubleGenerator Instances of ByteToDoubleGenerator represent generator functions which take bytes as input and yield sequences of values of type double.
ByteToFloat Instances of ByteToFloat represent functions which take bytes as input and return values of type float.
ByteToFloatGenerator Instances of ByteToFloatGenerator represent generator functions which take bytes as input and yield sequences of values of type float.
ByteToInt Instances of ByteToInt represent functions which take bytes as input and return values of type int.
ByteToIntGenerator Instances of ByteToIntGenerator represent generator functions which take bytes as input and yield sequences of values of type int.
ByteToLong Instances of ByteToLong represent functions which take bytes as input and return values of type long.
ByteToLongGenerator Instances of ByteToLongGenerator represent generator functions which take bytes as input and yield sequences of values of type long.
ByteToObject<V> Instances of ByteToObject represent functions which take bytes as input and return values of type V.
ByteToObjectGenerator<V> Instances of ByteToObjectGenerator represent generator functions which take bytes as input and yield sequences of values of type V.
ByteToShort Instances of ByteToShort represent functions which take bytes as input and return values of type short.
ByteToShortGenerator Instances of ByteToShortGenerator represent generator functions which take bytes as input and yield sequences of values of type short.
ByteToVoid Instances of ByteToVoid represent functions which take bytes as input and return values of type void.
ByteToVoidGenerator Instances of ByteToVoidGenerator represent generator functions which take bytes as input and yield sequences of values of type void.
CharAggregateState CharAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type char.
CharConsumer CharConsumer is a callback interface.
CharFilterState CharFilterState is the subinterface of FilterState that is used for filter methods with return value of type char.
CharToBoolean Instances of CharToBoolean represent functions which take chars as input and return values of type boolean.
CharToBooleanGenerator Instances of CharToBooleanGenerator represent generator functions which take chars as input and yield sequences of values of type boolean.
CharToByte Instances of CharToByte represent functions which take chars as input and return values of type byte.
CharToByteGenerator Instances of CharToByteGenerator represent generator functions which take chars as input and yield sequences of values of type byte.
CharToChar Instances of CharToChar represent functions which take chars as input and return values of type char.
CharToCharGenerator Instances of CharToCharGenerator represent generator functions which take chars as input and yield sequences of values of type char.
CharToDouble Instances of CharToDouble represent functions which take chars as input and return values of type double.
CharToDoubleGenerator Instances of CharToDoubleGenerator represent generator functions which take chars as input and yield sequences of values of type double.
CharToFloat Instances of CharToFloat represent functions which take chars as input and return values of type float.
CharToFloatGenerator Instances of CharToFloatGenerator represent generator functions which take chars as input and yield sequences of values of type float.
CharToInt Instances of CharToInt represent functions which take chars as input and return values of type int.
CharToIntGenerator Instances of CharToIntGenerator represent generator functions which take chars as input and yield sequences of values of type int.
CharToLong Instances of CharToLong represent functions which take chars as input and return values of type long.
CharToLongGenerator Instances of CharToLongGenerator represent generator functions which take chars as input and yield sequences of values of type long.
CharToObject<V> Instances of CharToObject represent functions which take chars as input and return values of type V.
CharToObjectGenerator<V> Instances of CharToObjectGenerator represent generator functions which take chars as input and yield sequences of values of type V.
CharToShort Instances of CharToShort represent functions which take chars as input and return values of type short.
CharToShortGenerator Instances of CharToShortGenerator represent generator functions which take chars as input and yield sequences of values of type short.
CharToVoid Instances of CharToVoid represent functions which take chars as input and return values of type void.
CharToVoidGenerator Instances of CharToVoidGenerator represent generator functions which take chars as input and yield sequences of values of type void.
DoubleAggregateState DoubleAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type double.
DoubleConsumer DoubleConsumer is a callback interface.
DoubleFilterState DoubleFilterState is the subinterface of FilterState that is used for filter methods with return value of type double.
DoubleToBoolean Instances of DoubleToBoolean represent functions which take doubles as input and return values of type boolean.
DoubleToBooleanGenerator Instances of DoubleToBooleanGenerator represent generator functions which take doubles as input and yield sequences of values of type boolean.
DoubleToByte Instances of DoubleToByte represent functions which take doubles as input and return values of type byte.
DoubleToByteGenerator Instances of DoubleToByteGenerator represent generator functions which take doubles as input and yield sequences of values of type byte.
DoubleToChar Instances of DoubleToChar represent functions which take doubles as input and return values of type char.
DoubleToCharGenerator Instances of DoubleToCharGenerator represent generator functions which take doubles as input and yield sequences of values of type char.
DoubleToDouble Instances of DoubleToDouble represent functions which take doubles as input and return values of type double.
DoubleToDoubleGenerator Instances of DoubleToDoubleGenerator represent generator functions which take doubles as input and yield sequences of values of type double.
DoubleToFloat Instances of DoubleToFloat represent functions which take doubles as input and return values of type float.
DoubleToFloatGenerator Instances of DoubleToFloatGenerator represent generator functions which take doubles as input and yield sequences of values of type float.
DoubleToInt Instances of DoubleToInt represent functions which take doubles as input and return values of type int.
DoubleToIntGenerator Instances of DoubleToIntGenerator represent generator functions which take doubles as input and yield sequences of values of type int.
DoubleToLong Instances of DoubleToLong represent functions which take doubles as input and return values of type long.
DoubleToLongGenerator Instances of DoubleToLongGenerator represent generator functions which take doubles as input and yield sequences of values of type long.
DoubleToObject<V> Instances of DoubleToObject represent functions which take doubles as input and return values of type V.
DoubleToObjectGenerator<V> Instances of DoubleToObjectGenerator represent generator functions which take doubles as input and yield sequences of values of type V.
DoubleToShort Instances of DoubleToShort represent functions which take doubles as input and return values of type short.
DoubleToShortGenerator Instances of DoubleToShortGenerator represent generator functions which take doubles as input and yield sequences of values of type short.
DoubleToVoid Instances of DoubleToVoid represent functions which take doubles as input and return values of type void.
DoubleToVoidGenerator Instances of DoubleToVoidGenerator represent generator functions which take doubles as input and yield sequences of values of type void.
FilterState An instance of FilterState is used in filter method invocations as specified by the XL programming language.
FloatAggregateState FloatAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type float.
FloatConsumer FloatConsumer is a callback interface.
FloatFilterState FloatFilterState is the subinterface of FilterState that is used for filter methods with return value of type float.
FloatToBoolean Instances of FloatToBoolean represent functions which take floats as input and return values of type boolean.
FloatToBooleanGenerator Instances of FloatToBooleanGenerator represent generator functions which take floats as input and yield sequences of values of type boolean.
FloatToByte Instances of FloatToByte represent functions which take floats as input and return values of type byte.
FloatToByteGenerator Instances of FloatToByteGenerator represent generator functions which take floats as input and yield sequences of values of type byte.
FloatToChar Instances of FloatToChar represent functions which take floats as input and return values of type char.
FloatToCharGenerator Instances of FloatToCharGenerator represent generator functions which take floats as input and yield sequences of values of type char.
FloatToDouble Instances of FloatToDouble represent functions which take floats as input and return values of type double.
FloatToDoubleGenerator Instances of FloatToDoubleGenerator represent generator functions which take floats as input and yield sequences of values of type double.
FloatToFloat Instances of FloatToFloat represent functions which take floats as input and return values of type float.
FloatToFloatGenerator Instances of FloatToFloatGenerator represent generator functions which take floats as input and yield sequences of values of type float.
FloatToInt Instances of FloatToInt represent functions which take floats as input and return values of type int.
FloatToIntGenerator Instances of FloatToIntGenerator represent generator functions which take floats as input and yield sequences of values of type int.
FloatToLong Instances of FloatToLong represent functions which take floats as input and return values of type long.
FloatToLongGenerator Instances of FloatToLongGenerator represent generator functions which take floats as input and yield sequences of values of type long.
FloatToObject<V> Instances of FloatToObject represent functions which take floats as input and return values of type V.
FloatToObjectGenerator<V> Instances of FloatToObjectGenerator represent generator functions which take floats as input and yield sequences of values of type V.
FloatToShort Instances of FloatToShort represent functions which take floats as input and return values of type short.
FloatToShortGenerator Instances of FloatToShortGenerator represent generator functions which take floats as input and yield sequences of values of type short.
FloatToVoid Instances of FloatToVoid represent functions which take floats as input and return values of type void.
FloatToVoidGenerator Instances of FloatToVoidGenerator represent generator functions which take floats as input and yield sequences of values of type void.
IntAggregateState IntAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type int.
IntConsumer IntConsumer is a callback interface.
IntFilterState IntFilterState is the subinterface of FilterState that is used for filter methods with return value of type int.
IntToBoolean Instances of IntToBoolean represent functions which take ints as input and return values of type boolean.
IntToBooleanGenerator Instances of IntToBooleanGenerator represent generator functions which take ints as input and yield sequences of values of type boolean.
IntToByte Instances of IntToByte represent functions which take ints as input and return values of type byte.
IntToByteGenerator Instances of IntToByteGenerator represent generator functions which take ints as input and yield sequences of values of type byte.
IntToChar Instances of IntToChar represent functions which take ints as input and return values of type char.
IntToCharGenerator Instances of IntToCharGenerator represent generator functions which take ints as input and yield sequences of values of type char.
IntToDouble Instances of IntToDouble represent functions which take ints as input and return values of type double.
IntToDoubleGenerator Instances of IntToDoubleGenerator represent generator functions which take ints as input and yield sequences of values of type double.
IntToFloat Instances of IntToFloat represent functions which take ints as input and return values of type float.
IntToFloatGenerator Instances of IntToFloatGenerator represent generator functions which take ints as input and yield sequences of values of type float.
IntToInt Instances of IntToInt represent functions which take ints as input and return values of type int.
IntToIntGenerator Instances of IntToIntGenerator represent generator functions which take ints as input and yield sequences of values of type int.
IntToLong Instances of IntToLong represent functions which take ints as input and return values of type long.
IntToLongGenerator Instances of IntToLongGenerator represent generator functions which take ints as input and yield sequences of values of type long.
IntToObject<V> Instances of IntToObject represent functions which take ints as input and return values of type V.
IntToObjectGenerator<V> Instances of IntToObjectGenerator represent generator functions which take ints as input and yield sequences of values of type V.
IntToShort Instances of IntToShort represent functions which take ints as input and return values of type short.
IntToShortGenerator Instances of IntToShortGenerator represent generator functions which take ints as input and yield sequences of values of type short.
IntToVoid Instances of IntToVoid represent functions which take ints as input and return values of type void.
IntToVoidGenerator Instances of IntToVoidGenerator represent generator functions which take ints as input and yield sequences of values of type void.
LongAggregateState LongAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type long.
LongConsumer LongConsumer is a callback interface.
LongFilterState LongFilterState is the subinterface of FilterState that is used for filter methods with return value of type long.
LongToBoolean Instances of LongToBoolean represent functions which take longs as input and return values of type boolean.
LongToBooleanGenerator Instances of LongToBooleanGenerator represent generator functions which take longs as input and yield sequences of values of type boolean.
LongToByte Instances of LongToByte represent functions which take longs as input and return values of type byte.
LongToByteGenerator Instances of LongToByteGenerator represent generator functions which take longs as input and yield sequences of values of type byte.
LongToChar Instances of LongToChar represent functions which take longs as input and return values of type char.
LongToCharGenerator Instances of LongToCharGenerator represent generator functions which take longs as input and yield sequences of values of type char.
LongToDouble Instances of LongToDouble represent functions which take longs as input and return values of type double.
LongToDoubleGenerator Instances of LongToDoubleGenerator represent generator functions which take longs as input and yield sequences of values of type double.
LongToFloat Instances of LongToFloat represent functions which take longs as input and return values of type float.
LongToFloatGenerator Instances of LongToFloatGenerator represent generator functions which take longs as input and yield sequences of values of type float.
LongToInt Instances of LongToInt represent functions which take longs as input and return values of type int.
LongToIntGenerator Instances of LongToIntGenerator represent generator functions which take longs as input and yield sequences of values of type int.
LongToLong Instances of LongToLong represent functions which take longs as input and return values of type long.
LongToLongGenerator Instances of LongToLongGenerator represent generator functions which take longs as input and yield sequences of values of type long.
LongToObject<V> Instances of LongToObject represent functions which take longs as input and return values of type V.
LongToObjectGenerator<V> Instances of LongToObjectGenerator represent generator functions which take longs as input and yield sequences of values of type V.
LongToShort Instances of LongToShort represent functions which take longs as input and return values of type short.
LongToShortGenerator Instances of LongToShortGenerator represent generator functions which take longs as input and yield sequences of values of type short.
LongToVoid Instances of LongToVoid represent functions which take longs as input and return values of type void.
LongToVoidGenerator Instances of LongToVoidGenerator represent generator functions which take longs as input and yield sequences of values of type void.
ObjectAggregateState<T> ObjectAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type T.
ObjectConsumer<T> ObjectConsumer is a callback interface.
ObjectFilterState<T> ObjectFilterState is the subinterface of FilterState that is used for filter methods with return value of type T.
ObjectToBoolean<K> Instances of ObjectToBoolean represent functions which take Ks as input and return values of type boolean.
ObjectToBooleanGenerator<K> Instances of ObjectToBooleanGenerator represent generator functions which take Ks as input and yield sequences of values of type boolean.
ObjectToByte<K> Instances of ObjectToByte represent functions which take Ks as input and return values of type byte.
ObjectToByteGenerator<K> Instances of ObjectToByteGenerator represent generator functions which take Ks as input and yield sequences of values of type byte.
ObjectToChar<K> Instances of ObjectToChar represent functions which take Ks as input and return values of type char.
ObjectToCharGenerator<K> Instances of ObjectToCharGenerator represent generator functions which take Ks as input and yield sequences of values of type char.
ObjectToDouble<K> Instances of ObjectToDouble represent functions which take Ks as input and return values of type double.
ObjectToDoubleGenerator<K> Instances of ObjectToDoubleGenerator represent generator functions which take Ks as input and yield sequences of values of type double.
ObjectToFloat<K> Instances of ObjectToFloat represent functions which take Ks as input and return values of type float.
ObjectToFloatGenerator<K> Instances of ObjectToFloatGenerator represent generator functions which take Ks as input and yield sequences of values of type float.
ObjectToInt<K> Instances of ObjectToInt represent functions which take Ks as input and return values of type int.
ObjectToIntGenerator<K> Instances of ObjectToIntGenerator represent generator functions which take Ks as input and yield sequences of values of type int.
ObjectToLong<K> Instances of ObjectToLong represent functions which take Ks as input and return values of type long.
ObjectToLongGenerator<K> Instances of ObjectToLongGenerator represent generator functions which take Ks as input and yield sequences of values of type long.
ObjectToObject<K,V> Instances of ObjectToObject represent functions which take Ks as input and return values of type V.
ObjectToObjectGenerator<K,V> Instances of ObjectToObjectGenerator represent generator functions which take Ks as input and yield sequences of values of type V.
ObjectToShort<K> Instances of ObjectToShort represent functions which take Ks as input and return values of type short.
ObjectToShortGenerator<K> Instances of ObjectToShortGenerator represent generator functions which take Ks as input and yield sequences of values of type short.
ObjectToVoid<K> Instances of ObjectToVoid represent functions which take Ks as input and return values of type void.
ObjectToVoidGenerator<K> Instances of ObjectToVoidGenerator represent generator functions which take Ks as input and yield sequences of values of type void.
ShortAggregateState ShortAggregateState is the subinterface of AggregateState that is used for aggregate methods with return value of type short.
ShortConsumer ShortConsumer is a callback interface.
ShortFilterState ShortFilterState is the subinterface of FilterState that is used for filter methods with return value of type short.
ShortToBoolean Instances of ShortToBoolean represent functions which take shorts as input and return values of type boolean.
ShortToBooleanGenerator Instances of ShortToBooleanGenerator represent generator functions which take shorts as input and yield sequences of values of type boolean.
ShortToByte Instances of ShortToByte represent functions which take shorts as input and return values of type byte.
ShortToByteGenerator Instances of ShortToByteGenerator represent generator functions which take shorts as input and yield sequences of values of type byte.
ShortToChar Instances of ShortToChar represent functions which take shorts as input and return values of type char.
ShortToCharGenerator Instances of ShortToCharGenerator represent generator functions which take shorts as input and yield sequences of values of type char.
ShortToDouble Instances of ShortToDouble represent functions which take shorts as input and return values of type double.
ShortToDoubleGenerator Instances of ShortToDoubleGenerator represent generator functions which take shorts as input and yield sequences of values of type double.
ShortToFloat Instances of ShortToFloat represent functions which take shorts as input and return values of type float.
ShortToFloatGenerator Instances of ShortToFloatGenerator represent generator functions which take shorts as input and yield sequences of values of type float.
ShortToInt Instances of ShortToInt represent functions which take shorts as input and return values of type int.
ShortToIntGenerator Instances of ShortToIntGenerator represent generator functions which take shorts as input and yield sequences of values of type int.
ShortToLong Instances of ShortToLong represent functions which take shorts as input and return values of type long.
ShortToLongGenerator Instances of ShortToLongGenerator represent generator functions which take shorts as input and yield sequences of values of type long.
ShortToObject<V> Instances of ShortToObject represent functions which take shorts as input and return values of type V.
ShortToObjectGenerator<V> Instances of ShortToObjectGenerator represent generator functions which take shorts as input and yield sequences of values of type V.
ShortToShort Instances of ShortToShort represent functions which take shorts as input and return values of type short.
ShortToShortGenerator Instances of ShortToShortGenerator represent generator functions which take shorts as input and yield sequences of values of type short.
ShortToVoid Instances of ShortToVoid represent functions which take shorts as input and return values of type void.
ShortToVoidGenerator Instances of ShortToVoidGenerator represent generator functions which take shorts as input and yield sequences of values of type void.
VoidConsumer VoidConsumer is a callback interface.
VoidToBoolean Instances of VoidToBoolean represent functions which take voids as input and return values of type boolean.
VoidToBooleanGenerator Instances of VoidToBooleanGenerator represent generator functions which take voids as input and yield sequences of values of type boolean.
VoidToByte Instances of VoidToByte represent functions which take voids as input and return values of type byte.
VoidToByteGenerator Instances of VoidToByteGenerator represent generator functions which take voids as input and yield sequences of values of type byte.
VoidToChar Instances of VoidToChar represent functions which take voids as input and return values of type char.
VoidToCharGenerator Instances of VoidToCharGenerator represent generator functions which take voids as input and yield sequences of values of type char.
VoidToDouble Instances of VoidToDouble represent functions which take voids as input and return values of type double.
VoidToDoubleGenerator Instances of VoidToDoubleGenerator represent generator functions which take voids as input and yield sequences of values of type double.
VoidToFloat Instances of VoidToFloat represent functions which take voids as input and return values of type float.
VoidToFloatGenerator Instances of VoidToFloatGenerator represent generator functions which take voids as input and yield sequences of values of type float.
VoidToInt Instances of VoidToInt represent functions which take voids as input and return values of type int.
VoidToIntGenerator Instances of VoidToIntGenerator represent generator functions which take voids as input and yield sequences of values of type int.
VoidToLong Instances of VoidToLong represent functions which take voids as input and return values of type long.
VoidToLongGenerator Instances of VoidToLongGenerator represent generator functions which take voids as input and yield sequences of values of type long.
VoidToObject<V> Instances of VoidToObject represent functions which take voids as input and return values of type V.
VoidToObjectGenerator<V> Instances of VoidToObjectGenerator represent generator functions which take voids as input and yield sequences of values of type V.
VoidToShort Instances of VoidToShort represent functions which take voids as input and return values of type short.
VoidToShortGenerator Instances of VoidToShortGenerator represent generator functions which take voids as input and yield sequences of values of type short.
VoidToVoid Instances of VoidToVoid represent functions which take voids as input and return values of type void.
VoidToVoidGenerator Instances of VoidToVoidGenerator represent generator functions which take voids as input and yield sequences of values of type void.
Aggregate An instance of Aggregate is used in aggregate method invocations as specified by the XL programming language.
Filter An instance of Filter is used in filter method invocations as specified by the XL programming language.
Autoconversion If the compiler flag EnableAutoconversionAnnotation is enabled, only functions tagged with this annotation are subject to autoconversion.

matches: V. V. V. V. V. V. V. V. V. V. V. V. V. V. V. V. V. V. V. V.


Fenton Hill, NM. Photo: courtesy of Los Alamos National Laboratory.
Under the deep blue skies of northern New Mexico in the fall of 1974, drillmen labored to extract cores from a borehole called GT-2 (Figure 1) nearly three miles deep. The site was Fenton Hill, on the west flank of the Valles volcanic caldera in the pine-covered Jemez Mountains. Two dozen miles to the east, geoscientists at Los Alamos National Laboratory analyzed the drill cores, investigating whether the hot, dry rock would be suitable for providing geothermal energy.
The geoscientists identified the rock as biotite granodiorite, a granitic rock containing shiny flecks of a black mica called biotite. They crushed a core sample from a depth of 2,900 meters and extracted microscopic crystals of zirconium silicate (ZrSiO4) embedded in the biotite. These crystals, called zircons, were radioactive, containing high amounts of uranium and thorium relative to the rest of the rock, as is usual for that mineral. Comparing two isotopes of radiogenic(formed by nuclear decay) lead (206Pb from 238U and 207Pb from 235U), they determined that 1,500 ± 20 million years worth of nuclear decay had occurred in the zirconsassuming as usual that nuclear decay rates have always been constant (Zartman, 1979). The date is consistent with uniformitarian expectations for this Precambrian “basement” rock unit.
Figure 2. Uranium, lead, and helium in a schematic zircon. 238U decaying to 206Pb releases eight alpha particles (which become helium atoms) within the crystal.
Figure 3. Zircons 50 to 75 µm long extracted by Gentry et al. (1982a) from GT-2 core samples. Photo: courtesy of R. V. Gentry.
The zircons also would be expected to contain helium (4He), which comes from the alpha particles (nuclei of helium atoms) emitted by many of the nuclear decays (Figure 2). This prompted Robert Gentry at Oak Ridge National Laboratory to ask the Los Alamos team to send him core samples from various depths in GT-2 (as well as samples from deeper boreholes nearby). Gentry and his team extracted zircons from the samples, hand-picked crystals between 50 and 75 microns long (Figure 3), and measured the total amounts of helium in them. From the amounts of radiogenic lead in the zircons, they estimated how much helium the nuclear decay should have deposited in the crystals. They found that “an almost phenomenal amount of He has been retained” in the zircons, despite them being small, hot, and allegedly old (Gentry et al., 1982a). Table I shows their results as samples 1 through 6.
Note carefully: Gentry’s large retentions are not what uniformitarians mean by “excess helium” (Baxter, 2003), a common mental pigeonhole into which they shove helium anomalies. In the context of these zircons, “excess” helium would correspond to retentions greater than 100% of the amount nuclear decay could produce in 1.5 Gyr. We are not claiming such “excess” helium at all. As we explain in “Latest results arrive in mid-2003” on page 8 of this paper, the uniformitarian method of “helium dating,” called (U-Th)/He chronometry, is entirely different from the helium diffusion dating we are employing here. Uniformitarian “helium dating” methods would not call attention to the large helium retentions we are concerned with, so it may be that sites like borehole GT-2 are common throughout the world.
When creationists became aware of Gentry’s data, many of us thought that it would have been impossible for the zircons to have retained that much helium for even a million years, much less over a billion years. Helium is a lightweight, fast-moving atom that does not attach itself to other atoms, so it diffuses (spreads out) through the atomic lattices of most minerals relatively fast. However, we knew of only one published measurement of diffusion rates of helium through zircon (Magomedov, 1970). That report was sketchy and ambiguous, leaving room for quite different ways to interpret the numbers. There were no published measurements for helium diffusion through biotite, the mineral surrounding the zircons. Until we had reliable numbers for these diffusion rates, we could not say for certain that the large retentions require a young earth.
Table I: Observed helium retentions for zircons recovered from various depths in borehole GT-2 and others nearby, Fenton Hill, NM. Samples 2002 and 2003 were recovered for the RATE project and named for the years we analyzed them. Samples 1-6 are those reported by Gentry et al. (1982a). Column 4 is the total helium yield (1 ncc = 10-9cm3 at standard temperature and pressure) per microgram of zircon. Column 5 is the corresponding fraction of the estimated amount of helium deposited in the zircons by nuclear decay. Column 6 is the estimated error in the fraction. All zircons were of length 50-75 µm, except for those from sample 2002, which were not sorted into size groups.
In 1998, the Radioisotopes and the Age of the Earth (RATE) steering committee began planning to do experiments to measure helium diffusion in the relevant minerals. RATE (Vardiman et al., 2003) is a research initiative started in 1997 by seven scientists from three major creationist organizations: the Institute for Creation Research (ICR), Answers in Genesis (AiG), and the Creation Research Society (CRS). In 1998 a personnel transfer reduced the sponsoring organizations from three to two, ICR and CRS. Three board members of CRS have been on the RATE steering committee from the outset: Donald DeYoung, Eugene Chaffin, and Russell Humphreys. CRS members have supported the project by designating donations to the RATE research fund administered by ICR.
The charter for RATE was to make a focused investigation of the problem posed by two large bodies of geoscience evidence for (A) large amounts of nuclear decay having occurred, and (B) a young world. From the start, several members of the steering committee were convinced that episodes of greatly accelerated nuclear decay rates had occurred within thousands of years ago. For the preservation of life, such episodes seem possible only under special circumstances: (1) before God created living things, (2) after the Fall but well beneath the biosphere, and (3) during the year of the Genesis Flood, when the occupants of Noah’s ark would be safe from most radiation (Humphreys, 2000, pp. 340-341). Accordingly, the steering committee planned a research program to test the accelerated decay hypothesis, and they wrote a book (jointly published by ICR and CRS) outlining the various projects (Vardiman et al., 2000).
In developing our plans for the helium experiments, we calculated what diffusion rates would be necessary to produce Gentry’s reported helium retentions if the zircons were (a) 6,000 years old, or (b) 1.5 billion years old. Figure 4 shows the graph we published (Humphreys, 2000, p. 348, Figure 7) of the resulting two models.
Figure 4, the prediction, is a typical Arrhenius plot. The vertical axis shows diffusivities (giving rates of diffusion) logarithmically. The horizontal axis shows inverse absolute temperature (1000 divided by degrees Kelvin) linearly. High temperatures are on the left and low temperatures are on the right. Diffusion data on such a plot usually fall into one or two straight lines (Humphreys et al., 2003a, § 3). Notice that the diffusion rates in the Uniformitarian model are over 100,000 times slower (to retain helium 1.5 billion years) than those in the Creation model (6,000 years). Such a large difference made it likely that experiments would be able to distinguish between the two models, so we began seeking ways to conduct or commission such measurements.
In 2000, through an intermediary, we contracted with a well recognized expert (Humphreys et al., 2003a, § 5) to measure helium diffusion rates in biotite, the mineral we thought was the main restriction to helium loss from the zircons. We sent the experimenter biotite we had on hand, from the Beartooth Gneiss in Wyoming near Yellowstone National Park. In early 2001 he sent us data, the first ever reported on biotite. Also in 2001, we received a preprint of a paper reporting helium diffusion rates measured in zircons from Nevada (Reiners et al., 2002).
Figure 4. Predicted (Humphreys, 2000, p. 348, Figure 7) helium diffusion rates necessary to retain the observed amounts of helium (Table I) for (a) 6,000 years (Creation model), or (b) 1.5 billion years (Uniformitarian model).
These data quickly showed us that the zircon itself, not the surrounding biotite, was the main restriction to helium outflow. But we found that when we modified the theoretical model accordingly (see appendix of this paper, page 14, discussion on change 5), the diffusivities in our prediction changed by less than 0.5 percent (Humphreys et al., 2003a, § 6). So the numbers of the prediction in Figure 4 are valid, but they should be applied to zircon, not biotite.
The Nevada zircon data agreed encouragingly with our prediction, but did not extend to low enough temperatures to overlap it. Moreover, those zircons were not from the New Mexico site. Neither were the biotites. Because helium diffusion in minerals can vary significantly from site to site, we decided to get data on biotites and zircons from the same borehole, GT-2, from which Gentry’s zircons came. Los Alamos National Laboratory kindly gave us several GT-2 core samples from a depth of 750 meters. That is somewhat shallower than Gentry’s samples, but still in the same rock unit. We sent one of them to Activation Laboratories in Ontario, Canada, where Jakov Kapusta extracted the biotite and zircons. He did not separate the zircons into size groups. He measured the uranium and lead isotopes in three of the zircons, finding a 206Pb/207Pb age of 1439 ± 2 million years (Humphreys et al., 2003a, Appendix A). That is within a few percent of the published age for zircons deeper in the borehole (this paper, page 1).
Then we sent both the biotite and the zircons to our experimenter. He sieved the biotite sample to get flakes between 75 and 100 µm, but he used all the zircons Kapusta extracted, regardless of size. Size of crystals (effective radius) is important in converting the raw data into diffusivities. He sent us the raw data in 2002.
As before, in the temperature range of interest to us, the biotite diffusivities were about one order of magnitude greater than those of zircon. That confirmed that the zircon rates were more important. Those data lined up well with the prediction, but again did not extend to low enough temperatures to overlap it (Humphreys et al., 2003a, § 8, Figure 8).
After that, in the summer and fall of 2002, we tried several times to get lower-temperature data. However, we only discovered several wrong ways to make such measurements. First, we asked the experimenter to do new runs on the same batch of zircons, but at lower temperatures. The results were ambiguous, an effect we decided was due to exhaustion of helium from the smaller zircons in the batch (Fechtig and Kalbitzer, 1966, § 2.5, p. 72).
Second, we sent the experimenter a new set of zircons from the same depth in GT-2 and asked him to sieve out crystals in the 5075 µm size range. Before sieving, he decided to leach the crystals in cold concentrated hydrofluoric acid (HF) to remove flecks of biotite clinging to them. Though the technique was new, it seemed reasonable. However, the values of D/a2 he then obtained were over fifty times higher than all previous zircon data, both ours and published. Scanning electron microscope images done later (see next section) revealed severe pitting and cracking in the HF-treated zircons. That would allow helium to leave the zircons much faster than normally.
These were all the data we had by February 2003, the deadline for the final version of our conference paper (Humphreys et al., 2003a).
In the fall of 2002, we acquired new samples from borehole GT-2, this time from a depth of 1490 meters. That is between the depths of Gentry’s samples 1 and 2 (see Table I). We sent them to Activation Laboratories, where Kapusta extracted both biotites and zircons. This time he sorted the zircons into several size groups, getting about 1200 crystals in the size range Gentry used, having lengths of 50-75 µm.
Figure 5 shows a scanning electron microscope (SEM) image of one such zircon. Mark Armitage obtained the image in his newly established microscopy laboratory at ICR, where he also obtained SEM images of the HF-treated zircons the previous section mentioned. In the spring of 2003, we sent our experimenter the 5075 µm zircons, along with the biotites. This time we asked him (a) not to etch the crystals in HF (unnecessary because no sieving was needed) and (b) to get zircon diffusivities at lower temperatures. We also asked that he measure more precisely the total helium per unit mass in both the zircons and the biotites. In July 2003, one month before the conference, we received his results.
Figure 5. Scanning electron microscopy photograph by Mark Armitage of zircon from group selected by size by Jakov Kapusta.
Table II: Latest (2003) helium diffusion data for 5075 µm length zircons from borehole GT-2 at a depth of 1490 meters. Column 3 is the amount of helium released (ncc defined in Table I) at the given temperature step. Column 4 is the time at each step. Column 5 is the cumulative fraction of the total helium yield (at bottom of table). Column 6 is the value of D/a2 estimated by the experimenter according to standard formulas, where D is the diffusivity and a is the average effective radius. Column 7 is the value of D assuming a = 30 µm, and omitting steps 1-9 according to advice from the experimenter (see below).
As usual, the experimenter measured the rate of helium release at various steps of temperature. Then he placed that data into standard formulas to calculate D/a2, where D is the diffusivity and a is the effective radius of the crystals. Column 6 of Table II shows the resulting values of D/a2 for the zircons. The standard formulas (Fechtig and Kalbitzer, 1966, p. 71) assume that the initial distribution of helium in the zircons is uniform. But in reality, the zircons would have a “rounded” helium-versus-radius profile due to the in situ helium loss into the biotite. That is, less helium would emerge during the initial heating steps, because the outer regions of the zircon would be helium-depleted. In that case, said the devisers of the standard formulas (Fechtig and Kalbitzer, 1966, p. 71), “The apparent diffusion constants will come out too low, and the activation energies too high.” In his report on the 2002 zircon runs (Humphreys et al., 2003, Appendix C), our experimenter advised us that to account for this effect, we should ignore the first set of increasing-temperature steps in his runs. For the 2003 zircons, he reported that we should treat them just the same. Accordingly, we ignored steps 1-9 in calculating D. A more sophisticated analysis could probably extract accurate values of D from the raw helium-time data for those steps, but we leave that work for later research.
The effective radius a for zircons is about half their length (Humphreys et al., 2003a, § 6), which in this case gives us an average value for a of about 30 µm. Multiplying column 6 by the resulting value of a2 gives us values of the diffusivity D for points 10-28, which we show in column 7 of Table II.
Figure 6 shows those values, plotted with the two models for comparison. The data agree with the predicted Creation model—as close as errors in the data and approximations in the model would lead us to expect. The data points extend past the “knee” of the model at 197º C, into the lower-temperature “defect” region determined by radiation damage in the crystals. This was quite important to examine, because the defect part of the curve can vary greatly from site to site (Humphreys et al., 2003a, §§ 3, 4). Even in the defect region, the data agree quite well with the model. It is not often in science that experimental data so clearly validate a pre-published numerical model!
Figure 6. Recent (2003) zircon diffusion rate data compared with the Creation and Uniformitarian models shown in Figure 4.
The data also resoundingly reject the Uniformitarian model. The points of that model are the values of diffusivity required to retain the observed amounts of helium for 1.5 billion years at today’s temperatures in the rock unit. However, uniformitarian thermal models of the rock unit require that the temperatures have been higher in the past (Kolstad and McGetchin, 1978; Harrison et al., 1986; Sakada, 1989). So the points of our Uniformitarian model are below the average temperatures during the alleged eons. A more accurate depiction would slide the Uniformitarian model points horizontally leftward to represent the allegedly higher average temperatures. That would make the vertical gap between that model and the data even larger (Humphreys et al., 2003b, see poster and extended temperature range Arrhenius plot at its bottom). Thus the Uniformitarian model in Figure 6 is very generous to uniformitarians, minimizing the gap. Even so, the data points are about 100,000 times higher than the model points. Uniformitarianism has totally failed this experimental test!
We can also compare the new diffusivities with the observed retentions to calculate the age of the zircons. Doing that point-by-point gives an average of 5,681 years with a sigma (square root of variance) of 1,999 years (Table III). We round that off to 6,000 ± 2,000 years.
Note carefully: Our diffusion dating method above differs entirely from the “helium dating” of (U-Th)/He chronometry (Reiners, 2002). Very crudely, the difference is this: (U-Th)/He chronometry divides the number of helium atoms in a crystal by nucleardecay rate. Diffusion dating divides the number of helium atoms lost from the crystal by the diffusion rate. It appears the practitioners of (U-Th)/He chronometry, in their unpublished comments upon this work, have not yet understood this basic distinction.
After stepwise heating the 216 micrograms of zircons to get the diffusivity data, our experimenter raised the temperature to a high value, holding it there long enough to get the rest of the helium out of the crystals. The total yield of helium from the zircons was 1356 ncc (1 ncc = 10-9 cm3 at standard temperature and pressure = 0.4462 x 10-4 nanomole), or 6.05 x 10-2 nmol. Dividing by the mass gives us 6.28 ncc/µg, or 303 nmol/g. Multiplying the latter value by the density of zircon, 4.7 g/cm3, gives us the helium concentration in the zircon: 1320 nmol/cm3.
For the 5.562 milligrams of biotite, the total yield of helium was 257 ncc, giving 2.06 nmol/g. Multiplying by the density of biotite, 3.2 grams/cm3, gives us the helium concentration in the biotite: 6.57 nmol/cm3.
These data are quite useful in closing possible loopholes in our case. First, the 6.3 ncc/µg yield of these zircons is quite consistent with Gentry’s retention data. Using Gentry’s estimate of radiogenic helium deposited in the zircons, about 15 ncc/µg (which is consistent with our data on radiogenic lead in the zircons), gives us a retention fraction of 0.42 (42%). These zircons came from a depth of 1490 meters, nearly midway between Gentry’s samples 1 and 2 in Table I. The interpolated temperature at that depth would be 124º C. Figure 7 shows that our new retention point fits quite well between Gentry’s retentions for samples 1 and 2. This confirms the validity of Gentry’s retention measurements.
Second, the concentration of helium in the zircon, 1320 nmol/cm3, is about 200 times greater than the concentration in the surrounding biotite, 6.6 nmol/cm3. Because the laws of diffusion require flow from greater to lesser concentrations, these data mean that helium is moving from the zircons into the biotite, not the other way around.
Third, because the average volume of the biotite flakes is hundreds of times greater than that of the zircons (Humphreys et al., 2003a, § 6), the amount of helium in the biotites is on the same order of magnitude as the amount of helium lost by the zircons. That rebuts a specious uniformitarian conjecture (Ross, 2003) that there could have been vast amounts (100,000 times greater than the already-large observed amounts) of non-radiogenic primordial helium in the zircons 1.5 billion years ago.
Table III: Estimates of age from Gentry’s helium retentions (Table I) and our measurements of helium diffusivity in the same zircons (Table II). Diffusivities here come from best exponential fits to nearby measured points from Table II, column 7. Because our lowest measured value for D is at 175° C, we extrapolated 24° C down to the temperature of sample 2 but not 45° C further down to that of sample 1. Then we calculated ages as we did in our ICC03 paper (Humphreys et al., 2003a, §§ 6 and 8), putting the x-values of ICC03 Table 2 and the values of D above into ICC03 equation 17 to get the values for the age t we show above. See our comments on page 9 (related to Figure 8) about sample 3, which above has the greatest deviation from the average age. We report the average and sigma above as 6,000 ± 2,000 years.
Figure 7. Recent (2003) measurement of percentage helium retained for zircons from 1490 meters depth and 124º C, compared with percent retentions (points 1 and 2) measured by Gentry et al. (1982a) shown in Table I.
Our conference paper answers other commonly raised objections, including (1) a nearly automatic response among uniformitarians involving the geoscience concept of “closure temperature” (Humphreys et al., 2003a, § 10), and (2) the possibility that the rock unit was much cooler for most of its history. Two short answers are that (1) the closure temperature for these zircons happens to be relatively low, 128º C, permitting the zircons above that temperature to leak helium freely, and (2) the zircons would have to have been refrigerated cooler than minus 100º C in order to retain the helium for the alleged eons (Humphreys et al., 2003b, see poster and extended temperature range Arrhenius plot at its bottom). Our conference paper clarifies these points and adds other answers (Humphreys et al., 2003a, §§ 9, 10).
Our new helium retention fraction (0.42 at 124º C) can be treated the same way as we treated Gentry’s retention data to make a prediction of diffusion rates. That is, we can use our retention figure to calculate what value of D at 124º C would be required if the zircons were 6,000 years old. Figure 8 shows how this “retrodiction” point fits very well with the diffusion rate data and the Creation model prediction.
In Figure 8, we have redrawn the lines in accord with the new data. The largest outlier from the lines is the model point at 197º C. The difference suggests the true retention fraction for that sample might have been about half the fraction Gentry et al. reported (Table 1, sample 3). Whatever the cause, a two-fold discrepancy for one point pales into insignificance in light of the whopping 100,000-fold discrepancy between the observed diffusivities and all points of the Uniformitarian model!
Figure 8. Figure 6 with lines redrawn in accordance with the new (2003) data. Squares with temperatures below them are the diffusivities we predicted in 2000 on the basis of Gentry’s reported retentions (Table I, samples 1-5) and an age of 6,000 years. The star with “124º C” above it is the diffusivity required by our new retention datum (Table I, sample 2003, and page 9) and a 6,000-year age.
Lead also diffuses out of zircon, although much more slowly than helium does. In addition to studying helium, Gentry and his team (1982b) at Oak Ridge also studied lead retention in 50-75 µm zircons from the same rock unit. The deepest sample was from a depth of 4310 meters and a temperature of 313º C. The paper reports, “there was little or no differential Pb loss which can be attributed to the higher temperatures at greater depths.” Judging from their experimental error, their results mean that more than 90% of the lead generated by “1.5 billion years” worth of nuclear decay has remained in even the deepest, hottest zircons.
The diffusion rates for lead in zircon are known, and the article reports that at 200º C, it would take 50 billion years for 1% of the lead to diffuse out of a 50-µm zircon. However, the article does not report such times for higher temperatures. Using the same equation and data (Gentry et al., 1982b, note 16; Magomedov, 1970), we calculate that at the highest borehole temperature, 313º C, a zircon 60 µm long (a = 30 µm) would lose about 50% of its lead in 1.5 billion years. Because the observations show that those zircons did not lose anywhere near that much lead, these data imply an age much less than 1.5 billion years. Thus the lead diffusion data support the young helium diffusion age of the zircons.
Experiments have strongly vindicated what creationists felt when Gentry reported the high helium retentions over twenty years ago. The helium indeed could not have remained in the zircons for even a million years, much less the alleged 1.5 billion years. Even more exciting, the most recent experiments give a helium diffusion age of 6,000 ± 2,000 years, which resonates strongly with the date of creation we get from a straightforward Biblical chronology.
Figure 9 illustrates the contrast between this helium age and the radioisotopic age. It shows two different “hourglasses,” representing helium diffusion and uranium-to-lead nuclear decay. These hourglasses give drastically different dates.
Figure 9. Two hourglasses representing dating by (a) helium diffusion and (b) uranium-lead decay. “Valve” represents possible nuclear decay acceleration.
We have much data to show that we have read the helium hourglass correctly: (1) Uranium-lead data give us the initial amount of sand (helium) in the top half (the zircon). (2) Gentry’s measurements, confirmed by ours, give us the present amount of sand in the top half. (3) Our diffusion rate experiments show how fast sand is presently trickling (diffusing) out of the top half into the bottom half (the biotite). (4) Our measurements show roughly the right amount of sand in the bottom half (helium in the biotite). (5) A third hourglass representing lead diffusion, though crude, agrees with the helium result.
For the nuclear decay hourglass, we also know similar things: present amounts in the top half (uranium in the zircon), the present trickling rate (nuclear decay rates), and the amounts in the bottom half (lead isotopes in the zircon). The large amount of helium, the actual alpha particles from the decays, confirms that a large amount of nuclear decay has taken place.
One way to reconcile these two hourglass readings is to suggest that one of them has a “valve” at its bottleneck controlling the trickling rate, a valve that was adjusted drastically in the past, possibly by direct intervention from God.
Long-agers might want to imagine that the valve is on the helium hourglass, and that for billions of years, diffusion rates were over 100,000 times slower until a few thousand years ago. But diffusion rates are tied straightforwardly to the laws of atomic physics, which are in turn intimately connected to the biochemical processes that sustain life. It is difficult to imagine any such drastic difference in atomic physics that would have allowed life on earth to exist.
On the other hand, it is much simpler to imagine that the valve is on the nuclear decay hourglass. Nuclear forces affect only a tiny region at the center of the atom. They have very little effect on the electronic structure of the atom or its chemical interactions. Moreover, a relatively small change in nuclear forces can cause a billion-fold acceleration of nuclear decay rates (Chaffin, 2003; Chaffin, 2000; Humphreys, 2000). Finally, the preponderance of Biblical and geoscience evidence for a young world (Humphreys, 2000, pp. 337-339) points to a change that would only affect dating methods which depend on slowly-decaying nuclei.
Thus our new diffusion data support the main hypothesis of the RATE research initiative: that God drastically accelerated the decay rates of long half-life nuclei during the earth’s recent past. For a feasibility study of this hypothesisincluding God’s possible purposes for such acceleration, Biblical passages hinting at it, disposal of excess heat, preserving life on earth, and effects on stars, see Humphreys (2000, pp. 333-379). The last three problems are not yet fully solved, but we expect to see progress on them in future papers.
Other RATE projects (Vardiman et al., 2003) are providing other very exciting evidence supporting the hypothesis, such as precision radioisotope measurements (Snelling, et al., 2003a), carbon 14 in fossils and diamonds (Baumgardner et al., 2003a, 2003b), nuclear theory (Chaffin, 2003), and new radiohalo evidence (Snelling and Armitage, 2003; Snelling et al., 2003b). After submitting this paper for publication, we presented these new results in a poster and an abstract at the American Geophysical Union Annual Fall Meeting in San Francisco in December 2003 (Humphreys et al., 2003b). We also presented results from two other RATE projects there (Baumgardner et al., 2003b; Snelling et al. 2003b). RATE hopes to release both a final technical report and a layman’s book (authored by Don DeYoung) in the fall of 2005. These are exhilarating days for creation science!
We express our appreciation to Los Alamos National Laboratory for giving us the Fenton Hill samples, to Jakov Kapusta and Activation Laboratories, Ltd., for processing them, to Robert Gentry for his advice and help, to Mark Armitage for his microscope work, to Zodiac Mining and Manufacturing, Inc., for its services as intermediary, and especially to the donors whose generosity made this work possible.
Recently a critic sought very hard to find loopholes in our arguments. While none of his points had any significant impact on our conclusions, it is worthwhile to review the specifics of his critique and answer them here. The critic felt a crucial issue was the possibility that the interface between zircon and biotite might slow or stop helium diffusion because of helium having different chemical potentials or solubilities in those two minerals, or because of interface resistance between them due to other causes. In the next three sections we will explain those terms and quantify their effects.
where k is the Boltzmann constant. The first term on the right, the “entropy of mixing,” contains no information related to the forces between atoms. The second term, µ’, is of interest. It is the contribution from all other factors, particularly the interaction energy between helium and the other atoms of the crystal.
Because helium is one of the noble gases, we might suspect that it would have very little chemical attraction for any other atoms. In fact, helium is the least chemically active of all the noble gases (Holloway, 1968, p. 45, Table 2.1). Nevertheless it does exhibit a faint attraction for other atoms. Theory and experiments (Wilson et al., p. 936, Table XI) show that helium atoms adhere very slightly to the surfaces of alkali halide crystals, with interaction potentials on the order of a few hundred calories per mole of helium. The largest estimated potential is 293.4 cal/mol, at the “saddle point” between the sodium and fluorine ions at the surface of NaF. The smallest potential listed is beside a chlorine ion at the surface of NaCl, 111.7 cal/mol.
To make this mechanism a viable possibility for rescuing the uniformitarian scenario, the second term on the right-hand side must be: (1) of opposite sign to the first (Δµ’ must be negative, meaning helium is more attracted to zircon than biotite), and (2) large enough to reduce J to a level about 100,000 times lower than what the first term alone would give. That could reduce the helium flow enough to let the zircon retain the helium for 1.5 billion years. In the coolest sample we analyzed, at 100° C, the average thermal energy kT of the atoms was 0.0321 eV. Then |Δµ’/kT| would be less than 0.246 for that sample, and even smaller for the hotter samples. That makes the magnitude of the second term less than 25% of that of the first term for all the samples we analyzed. However, our upper bound on the value of Δµ’ based on the chemical affinity of helium with alkali halides is likely at least an order of magnitude larger than the actual value. So a magnitude of the second term less than 2.5% of the first term is probably more realistic. The second term obviously does not provide the large reduction of helium flow the uniformitarian scenario requires.
However, an even more basic consideration shows our measurement procedures have already accounted for such differences. We note that the magnitude of Δµ’ is several times greater for a zircon-vacuum interface than for a zircon-biotite interface. That is, the attraction of a helium atom for the biotite it is entering partly cancels its attraction for the zircon it is leaving. But our experimenter measured the diffusivities of zircons in a vacuum. So the zircon diffusivities we report in Table II already include the effect of a stronger interface reflection than would exist for the zircons in their natural biotite setting. So however strong or weak the “chemical potential” interface effect may be, our measured diffusivities already account for it in a way that is generous to the uniformitarian model.
Solubility in this context corresponds to the maximum number of helium atoms one gram of crystal can absorb per bar of pressure (Weast, 1986, p. 101). The critic used the term as a measure of the difficulty with which a helium atom could enter biotite. As a hypothetical example, if all the spaces between atoms in biotite were much smaller than the diameter of a helium atom, then helium could never enter the crystal, so helium would be completely insoluble in biotite. If an alpha-decaying nucleus inside the biotite were to generate a helium atom therein, then the atom could distort the lattice and push its way out. The crystal would have a small but non-zero helium diffusivity and zero solubility.
However, real minerals have non-zero solubilities. The solubilities of helium in obsidian and basaltic glass between 200 and 300° C, for example, are on the order of 50 nmol/g per bar (Jambon and Shelby, 1980, Fig 2c) and on the same order in other minerals (Broadhurst et al., 1992). The solubility of helium in biotite has not been measured (we were the first to measure even diffusivity for that pair of substances), so we must find a way to estimate its effect in this case.
One way is to consider the interaction potential part µ’ of the chemical potential we mentioned in the previous section. For a helium atom near the surface of a crystal, the gradient of the potential is negative, making the force attractive. But the force can become repulsive for a helium atom entering a tightly packed crystal. For example, imagine that a helium atom has to come very close to an oxygen atom. If their nuclei are closer together than 2.94 Å (1 Å = 1 angstrom = 1 x 10-8 cm ≈ diameter of a neutral hydrogen atom), the force between the two atoms is repulsive (Kar and Chakravarty, 2001, Table I σos column and gradient of their equation 2).
However the space between silicate sheets in biotite is much larger than that (Deer et al., 1962, Vol. 3, pp. 1-3, 55; Dahl, 1996, Figure 1 and Table 4). The large spacing is the reason the diffusivity of helium in biotite (Humphreys et al., 2003a, Figure 6b) is about ten times higher than in zircon, which has tighter spacing (Deer et al., 1962, Vol. I, pp. 59-68). The relative spacings and diffusivities imply the solubility of helium in biotite is greater than in zircon, so the force related to solubility, included in the gradient of µ’, would tend to push helium atoms out of zircon and into biotite. Hence their respective solubilities would not hinder helium outflow from the zircon but rather enhance it.
Our critic also postulated some type of interface resistance arising from special distortion of the crystalline lattices at the interface between zircon and biotite. We can model such hypothetical interface resistance (Crank, 1975, p. 40, § 3.4.1) as a very thin layer of very low diffusivity between the zircon and biotite. The concentration of helium would drop rapidly across the layer, approximating a discontinuous change of concentration between zircon and biotite. Such a layer might consist of physically or chemically altered zircon or biotite, and it would be at most a few dozen angstroms thick.
This is over ten billion times lower than the diffusivities we measured in biotite (Humphreys et al., 2003, Figure 6b) and zircon (this paper, Figure 8) at the same temperature, 197° C. To see whether this is an achievable value or not, let us examine an example the critic gave for physical alteration of the minerals at the zircon-biotite interface.
The critic suggested that when biotite crystallizes around a zircon, it possibly forms with its silicate sheets (along which are the cleavage planes) everywhere parallel to the surface of the zircon, so that the biotite wraps up the zircon like layers of cellophane. But in the thousands of zircon-containing biotite flakes that we ourselves have observed under the microscope (Snelling and Armitage, 2003; Snelling et al., 2003b), the silicate sheets remain parallel all the way to the edge of the zircon crystal and do not wrap around the included zircons. A Los Alamos report has a photo of a radiohalo in biotite from borehole GT-2 showing the biotite cleavage staying parallel to itself, running right up against the zircon, and not becoming parallel to the zircon surface (Laughlin and Eddy, 1977, Figure 6, p. 18). There is simply no observational support for the critic’s hypothesis that layers of biotite envelop an included zircon.
However, for the sake of having a specific illustration of interface resistance, let us indulge the critic and imagine that a few of the biotite layers closest to the zircon wrap around it. We will even imagine that there are no openings in the biotite wrapping at the edges and corners of the zircon faces. In that case, diffusion in the interface would have to take place in the harder direction, perpendicular to the silicate sheets rather than parallel to them.
That is over 400 million times greater than the maximum diffusivity, equation (A9), that a 30 Å interface could have to retain the helium for 1.5 Gyr. Hence such a hypothetical mechanism fails to account for the high helium retention we document. Moreover, as we have already indicated, there is no observational support for the sort of interface crystallographic structure our critic speculates might exist.
The critic also explored the effects of several changes in the assumptions of our models: (1) inserting a large interface resistance, (2) greatly increasing the creation model D for biotite, (3) decreasing the uniformitarian model D for biotite from infinity to that of zircon, (4) accounting for anisotropy of biotite and zircon, and (5) changing the effective radius a from our early value of 22 µm (Humphreys, 2000, p. 347) to our more recent and more appropriate value of 30 µm (Humphreys et al., 2003a, § 6, after equation 9).
We have discussed change (1) in the preceding section, showing that it is unrealistic. Change (2) increases the helium loss rate from the zircons by a factor of six, making it less realistic than our assumption, which had a worst-case effect of 30% (Humphreys et al., 2003a, § 6, after equation 9). Change (3) decreases the loss rate from zircons by a factor of six, but we think it is unrealistic for uniformitarians to demand an extremely low value of D for the biotite as well as the zircon.
Regarding mineral anisotropies (4), we point out two things: (a) switching from sphere to cylinder geometry (roughly approximating anisotropy effects) for the most important mineral (zircon) would alter the results by less than a factor of two, and (b) even a factor-of-ten reduction in the modeled diffusivity of the surrounding mineral (biotite) would change our results by less than 30% (Humphreys et al., 2003a, § 6 after equation 9). Thus, accounting for biotite anisotropy would affect our results by much less than 30%. As for zircon, anisotropy in it is probably just as negligible as it is in many other similarly shaped crystals, such as quartz. Both our experimenter and other diffusion experts have not assigned a high priority to investigating that possibility.
Change (5), the increase in effective radius a required by our better knowledge of zircons, by itself would have increased the model-required D‘s by a factor of about two. But our better knowledge also required another model change, from a “bubble” in biotite to a solid in biotite. This second change reduced the D‘s by about a factor of two. Because the two effects nearly cancelled each other out, the net change in predicted D was less than 0.5%. We explained these things in our ICC paper (Humphreys et al., 2003a, § 6), but perhaps not clearly enough.
The critic acknowledged that changes (2-5) would not come anywhere close to eliminating the 100,000-fold discrepancy between our data and any reasonable uniformitarian scenario. But he asserted that the several-fold sensitivity to changes in assumptions means that the close agreement between the creation model and the data was merely accidental. That may be a possibility, but it may also mean we exercised good theoretical judgment in choosing the simplifying assumptions for our prediction.
Finally, the critic proposed we postpone publication until (a) further theoretical and experimental investigations would close all alleged loopholes, and (b) until we have much more data supporting our case from boreholes all over the world. We disagree with him. On point (a), detractors can allege loopholes eternally, and we think we have addressed all the so-far-alleged loopholes well enough to place the burden of proof on the detractors.
On point (b), the critic was laboring under a misunderstanding. He reasoned that the possible scarcity of sites with what uniformitarians call “excess helium” meant that sites with high retentions and short helium diffusion ages are rare. As we explained at the ends of the introduction and the “Latest results arrive in mid-2003″section in this paper, those two concepts (excess helium and diffusion age) are fundamentally different. But even if he were correct, we feel that the data in this paper are so well established that immediate publication is warranted.
We thank Roger Lenard, a physicist at Sandia National Laboratories in Albuquerque, NM, for his expert advice on chemical thermodynamics, which helped us to prepare the “Solubility” and “Interface resistance” sections above.
Baumgardner, J. R., A. A. Snelling, D. R. Humphreys, and S. A. Austin. 2003a. Measurable 14C in fossilized organic materials: confirming the young earth Creation-Flood model. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp. 127-142. See http://www.icr.org/research/.
Baxter, E. F., 2003. Quantification of the factors controlling the presence of excess 40Ar or 4He, Earth and Planetary Science Letters 216:619-634.
Broadhurst, C. L., M. J. Drake, B. E. Hagee, and T. J. Bernatowicz. 1991. Solubility and partitioning of Ne, Ar, Kr, and Xe in minerals and synthetic basaltic melts, Geochimica et Cosmochimica Acta 56:709-723.
Chaffin, E. F. 2000. Theoretical mechanisms of accelerated nuclear decay. In Vardiman et al. (2000), Chapter 6, pp. 305-331.
——. 2003. Accelerated decay: theoretical models. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp. 3-15. See http://www.icr.org/research/ .
Crank, J. 1975. The Mathematics of Diffusion, second edition, Oxford University Press, Oxford.
Dahl, P. S. 1996. The crystal-chemical basis for Ar retention in micas: inferences from interlayer partitioning and implications for geochronology, Contributions to Mineral Petrology, 123:22-39.
Deer, W. A., R. A. Howe, and M. A. Zussman. 1962. Rock-Forming Minerals, Vol. I, Ortho- and Ring Silicates, Vol. III, Sheet Silicates, Longmans, Green, and Company, London.
Fechtig, H., and S. Kalbitzer. 1966. The diffusion of argon in potassium-bearing solids. In Potassium Argon Dating, O. A. Schaeffer and J. Zähringer, editors, Springer-Verlag, New York, pp. 68-107.
Gentry, R. V., G. J. Glish, and E. H. McBay. 1982a. Differential helium retention in zircons: implications for nuclear waste management, Geophysical Research Letters 9(10):1129-1130. After consulting with Dr. Gentry, we have corrected, in the fourth column of our Table I, two apparent typographical errors in the corresponding column of his table. One is in the units of the column (which should have been 10-9 cc/µg instead of 10-8 cc/µg); the other is in sample 4 of that column. The crucial fractions in column five were correctly reported, as we have confirmed with our data.
Gentry, R. V., T. J. Sworski, H. S. McKown, D. H. Smith, R. E. Eby, and W. H. Christie. 1982b. Differential lead retention in zircons: implications for nuclear waste containment, Science 216:296-298.
Harrison, T. M., P. Morgan, and D. D. Blackwell. 1986. Constraints on the age of heating at the Fenton Hill site, Valles Caldera, New Mexico, Journal of Geophysical Research 91(B2):1899-1908.
Holloway, J. H. 1968. Noble-Gas Chemistry, Methuen, London.
Humphreys, D.R. 2000. Accelerated nuclear decay: a viable hypothesis? In Vardiman et al. (2000), Chapter 7, pp. 333-379.
Humphreys, D. R., S. A. Austin, J. R. Baumgardner, and A. A. Snelling. 2003a. Helium diffusion rates support accelerated nuclear decay. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp. 175-195. See http://www.icr.org/research/ .
Jambon, A., and J. E. Shelby. 1980. Helium diffusion and solubility in obsidians and basaltic glass in the range 200-300° C, Earth and Planetary Science Letters 51:206-214.
Kar, S., and C. Chakravarty. 2001. Diffusional anisotropy of simple sorbates in silicalite, Journal of Chemical Physics A 105:5785-5793.
Kolstad, C. D., and T. R. McGetchin. 1978. Thermal evolution models for the Valles Caldera with reference to a hot-dry-rock geothermal experiment, Journal of Volcanology and Geothermal Research 3:197-218.
Laughlin, A. W., and A. C. Eddy. 1977. Petrography and geochemistry of Precambrian rocks from GT-2 and EE-1, Los Alamos Scientific Laboratory Report LA-6930-MS.
Magomedov, Sh. A. 1970. Migration of radiogenic products in zircon, Geokhimiya 1970(2):263-267 (in Russian). English abstract in Geochemistry International 7(1):203, 1970. English translation available from D. R. Humphreys.
Manning, J. R. 1968. Diffusion Kinetics for Atoms in Crystals, Van Nostrand, Princeton.
Reiners, P. W. 2002, (U-Th)/He chronometry experiences a renaissance, Eos, Transactions of the American Geophysical Union83(3):21, 26-27.
Reiners, P. W., K. A. Farley, and H. J. Hickes. 2002. He diffusion and (U-Th)/He thermochronometry of zircon: initial results from Fish Canyon Tuff and Gold Butte, Nevada, Tectonophysics 349(1-4):297-308.
Ross, H. N. 2003. Reasons to believe radio broadcast, September 18, 2003, 6 to 8 p.m. Pacific time. Moderator: Krista Bontrager. Studio participants: Hugh Ross, Fazale Rana, and Marge Harmon. Telephone participant: Roger Wiens. Broadcast archive web link and response at http://www. icr.org/headlines/rate-hughross.html .
Sakada, M. 1989. Fluid inclusion evidence for recent temperature increases at Fenton Hill hot dry rock test site west of the Valles Caldera, New Mexico, U.S. A., Journal of Volcanology and Geothermal Research 36:257-266.
Snelling, A. A. and M. H. Armitage. 2003. Radiohalosa tale of three granitic plutons. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp. 243-267. See http://www.icr.org/research/ .
Snelling, A. A., S. A. Austin, and W. A. Hoesch. 2003a. Radioisotopes in the diabase sill (upper Precambrian) at Bass Rapids, Grand Canyon, Arizona: an application and test of the isochron dating method. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp. 269-285. See http://www.icr.org/research/ .
Vardiman, L., A. A. Snelling, and E. F. Chaffin, editors. 2000. Radioisotopes and the Age of the Earth: A Young-Earth Creationist Research Initiative, Institute for Creation Research and the Creation Research Society, San Diego, CA.
Vardiman, L., S. A. Austin, J. R. Baumgardner, E. F. Chaffin, D. B. DeYoung, D. R. Humphreys, and A. A. Snelling. 2003. Radioisotopes and the age of the earth. In ICC03, Ivey, R. L., Jr., editor, Creation Science Fellowship, Pittsburgh, PA, pp.337-348. See http://www.icr.org/research/.
Weast, R. C. 1986. Editor, Handbook of Chemistry and Physics, 67th edition, CRC Press, Boca Raton, FL.
Wilson, J. W., J. H. Heinbockel, and R. A. Outlaw. 1988. Atomic forces between noble gas atoms, alkali ions, and halogen ions for surface interactions, Journal of Chemical Physics 89(2):929-937.
Zartman, R. E. 1979. Uranium, thorium, and lead isotopic composition of biotite granodiorite (Sample 9527-2b) from LASL Drill Hole GT-2, Los Alamos Scientific Laboratory Report LA-7923-MS.