text:
Radiation Oncology/Prostate/Node Positive

Long-term outcomes

 * RTOG 75-06 - PMID 9531359 — Ten-year outcomes for pathologic node-positive patients treated in RTOG 75-06. (Hanks GE, IJRBOP 1998).
 * Conclusion: A small fraction of node-positive patients are cured at 10-year follow-up by radiation therapy (2 of 90 with PSA +3 of 90 by clinical endpoints). Innovative treatment programs should be directed at node-positive patients in an effort to improve the fraction cured.

Local Therapy vs No Local Therapy

 * SEER/U. Colorado PMID 24661660 - "The Impact of Definitive Local Therapy for Lymph Node–Positive Prostate Cancer: A Population-Based Study " (Rusthoven CG, Int J Radiat Oncol Biol Phys 2014; 88 (5); 1064-1073. )
 * 1995-2005, 796 clinically node positive (cN+), 2991 pathologically node positive (pN+), analyzed as separate cohorts.
 * For cN+ patients, 43% had EBRT vs 57% had No Local Therapy (NLT). 10-yr OS 45% vs 29% (P<.001) (median OS 9.6 vs 5.9 yr)
 * For pN+ patients, 78% had local therapy (radical prostatectomy (RP) 57%, EBRT 10%, or both 11%) vs 22% had NLT. 10-yr OS 65% vs 42% (P<.001) (median OS 13.6 vs 8.3 years)
 * Local therapy beneficial across subgroups, including age >=70 years and multiple +lymph nodes
 * Secondary comparisons of RP vs EBRT and RP +/- Adjuvant EBRT: no significant differences between modalities. +Trend toward improved OS with RP + Adjuvant EBRT over RP alone (p=.08).
 * Conclusion: "RP and EBRT were associated with substantial improvements in OS and PCSS. The best available evidence suggests that patients with N1M0 PCa can achieve improved long-term survival outcomes with definitive local therapy and these strategies should be considered in appropriate candidates."
 * "Mixed Population Model" PMID 25680608 - authors propose a model to account for potential "under-ascertainment" of radiation data (ie, coding "no radiation" in observational databases [SEER, etc] when radiation was actually delivered to the patient [Jagsi Cancer 2012;118:333-341, Walker IJROBP 2013;86:686-693, Jagsi IJROBP 2014;90(1):11-24]):

Prostatectomy vs Radiotherapy

 * Ulm, Germany / U. Michigan PMID 15356680 -- Comparison of external radiation therapy vs radical prostatectomy in lymph node positive prostate cancer patients. (2004 Kuefer, Prostate Cancer Prostatic Dis. 2004;7(4):343-9.)
 * Retrospective. 102 pts RPX, 44 pts ERT. Adjuvant androgen ablation was given in 76 of 102 RPX, 21 of 44 ERT.
 * Conclusion : "In case of positive lymph nodes, RPX and ERT might be considered and need to be explained to the patient. For future treatment decisions, the presented findings and a potential survival benefit need to be evaluated in a larger prospective setting."

Radiotherapy alone
Dose for positive nodes:
 * From Fletcher, Texbook of Radiotherapy, 3rd ed. (1980) - For lymphangiogram positive pelvic nodes, extend field to L4-L5 interspace, 45 Gy to pelvis + boost positive nodes to a total of 55-60 Gy.

Hormonal therapy after prostatectomy
Randomized data:
 * Messing / ECOG EST-3886 (1988 - 93)
 * 7 years, 1999 PMID 10588962 Full text — "Immediate hormonal therapy compared with observation after radical prostatectomy and pelvic lymphadenectomy in men with node-positive prostate cancer." (Messing EM, N Engl J Med. 1999 Dec 9;341(24):1781-8.)
 * 98 pts. Pts were found to have node-positive disease after radical prostatectomy + pelvic lymphadenectomy. Randomized to adjuvant goserelin (or bilateral orchiectomy) vs observation until disease progression (based on local or distant disease progression, not PSA).
 * Median 7.1 yrs f/u. 77% (antiandrogen) vs 18% (obs) were alive with no evidence of recurrent disease and undetectable PSA. Death from any cause in 7 of 47 men (antiandrogen) vs 18 of 51 (obs), S.S.
 * Conclusion: survival benefit for immediate hormonal therapy. RT not used.
 * 12 years, 2006 PMID 16750497 -- "Immediate versus deferred androgen deprivation treatment in patients with node-positive prostate cancer after radical prostatectomy and pelvic lymphadenectomy." (Messing EM, Lancet Oncol. 2006 Jun;7(6):472-9.)
 * Median f/u 11.9 yr. Improved OS (HR=1.84), PCSS (HR=4.09), and PFS (HR=3.42).

Retrospective:
 * SEER/Medicare; 2009 (1991-1999) PMID 19047295 -- "Role of androgen deprivation therapy for node-positive prostate cancer." (Wong YN, J Clin Oncol. 2009 Jan 1;27(1):100-5.)
 * 731 pts treated with RP with positive regional LNs. 209 men received ADT within 120 days of RP. Compared men receiving adjuvant ADT vs those without adjuvant ADT.
 * OS: no sig difference between adjuvant ADT and non-ADT groups (HR 0.97).
 * CONCLUSION: "Deferring immediate ADT in men with positive lymph nodes after RP may not significantly compromise survival."

Adjuvant hormonal therapy plus RT
See also: Radiation Oncology/Prostate/Adjuvant RT page
 * Multicenter; 2014 (1988-2010) - Retrospective
 * PMID 25245445 -- "Impact of adjuvant radiotherapy on survival of patients with node-positive prostate cancer." (Abdollah F, J Clin Oncol. 2014 Dec 10;32(35):3939-47.)
 * 1107 pts, all N+ after radical prostatectomy with extended LN dissection (obturator, ext iliac, and hypogastric); median 15 nodes removed. Treated at Mayo Clinic or San Raffaele (Milan). All received lifelong adjuvant hormonal therapy; adjuvant RT in 34.9%. RT median dose to prostate bed: 66.6 - 70.2 Gy; whole pelvis treated in 70-85% to median dose 45-50.4 Gy.
 * Developed stratification into 5 risk groups based on 4 parameters (number of positive nodes, pathologic Gleason score, tumor stage, surgical margin status). Validated using SEER database.
 * Adjuvant RT associated with more favorable CSM (HR 0.37). Only 2 risk groups benefitted from RT: intermediate risk (1-2 LN, G 7-10, pT3b/pT4 or +SM) and high risk (3-4 LN).
 * Conclusion: "The beneficial impact of aRT on survival in patients with pN1 prostate cancer is highly influenced by tumor characteristics. Men with low-volume nodal disease (≤ two PLNs) in the presence of intermediate- to high-grade, non-specimen-confined disease and those with intermediate-volume nodal disease (three to four PLNs) represent the ideal candidates for aRT after surgery."
 * Comment: PMID 25847937 -- "External Validation of the Benefit of Adjuvant Radiotherapy for Pathologic N1M0 Prostate Cancer" (Rusthoven, Carlson, Kavanagh. J Clin Oncol. 2015 Jun 10;33(17):1987-8). Authors report a re-analysis of Abdollah et al's SEER external validation cohort using identical RPA risk stratification groups to the primary analysis by Abdollah et al. The re-analysis with identical risk stratifications validates an OS benefit in 'intermediate-risk' patients (1-2 +LNs, G 7-10, pT3b/pT4 or +SM) (multivariate HR 0.63, p=0.048), but unable to validate benefit in 'high-risk' patients (3-4 +LNs) (multivariate HR 1.17, p=0.729).

 * Italy, 2011 (1986-2002) - Retrospective, multi-center
 * 364 pts (of a series of 703 pts), pLN+ treated with RP. Matched analysis comparing 117 pts treated with HT + RT vs 247 pts treated with HT alone.
 * 2011 PMID 21354694 -- "Combination of adjuvant hormonal and radiation therapy significantly prolongs survival of patients with pT2-4 pN+ prostate cancer: results of a matched analysis." (Briganti A, Eur Urol. 2011 May;59(5):832-40.)
 * Median f/u 95 mo. (7.9 yr). 5/8-year CSS 90%/82%, OS 85%/70%. Pts treated with RT+HT had higher CSS and OS rates (5/8-year CSS: 95%/91% vs 88%/78%, OS: 90%/84% vs 82%/65%).
 * Conclusion: "Adjuvant RT plus HT significantly improved CSS and OS of pT2-4 pN1 patients, regardless of the extent of nodal invasion. These results reinforce the need for a multimodal approach in the treatment of node-positive prostate cancer."

 * Italy, 2009 (1988-2002) - Retrospective
 * Retrospective review of 250 consecutive pLN+ patients treated with RP, followed by HT alone (48%) or HT and RT (52%). Seventy-four percent of patients received pelvic and prostate bed RT. Median dose 66.6 Gy.
 * 2009 PMID 19211184 -- "Long-term follow-up of patients with prostate cancer and nodal metastases treated by pelvic lymphadenectomy and radical prostatectomy: the positive impact of adjuvant radiotherapy." (Da Pozzo LF, Eur Urol. 2009 May;55(5):1003-11.)
 * 5/8-year bRFS 72/61%, CSS 89/83%. In multivariate analysis, adjuvant RT and # of positive LN predicted bRFS and CSS. Patients treated with aHT alone had 2.6× risk of prostate cancer mortality vs. HT and RT after accounting for other predictors.

Hormonal therapy and radiotherapy

 * MD Anderson, 2001 (1984-1998) PMID 11489709 — "Addition of radiation therapy to androgen ablation improves outcome for subclinically node-positive prostate cancer."  Zagars GK, Pollack A, von Eschenbach AC. Urology. 2001 Aug;58(2):233-9.
 * Retrospective. 255 pts N+ found on lymphadenectomy treated with early androgen ablation alone (n=188) or with 70 Gy EBRT (n=72). Median F/U 9.4 years for ablation alone, 6.2 years for ablation + RT
 * 10 year outcome: Adding EBRT improved OS from 46 to 67%. Freedom from relapse improved from 25% to 80%
 * Conclusion: Early androgen ablation alone not helpful. Addition of RT offers substantial and significant improvement

 * RTOG 85-31: Subset Analysis, PMID 15681524 — "Androgen suppression plus radiation versus radiation alone for patients with stage D1/pathologic node-positive adenocarcinoma of the prostate: updated results based on national prospective randomized trial Radiation Therapy Oncology Group 85-31." Lawton CA et al. J Clin Oncol. 2005 Feb 1;23(4):800-7.
 * Updated analysis of pN+ pts (median f/u on all pts (6.5 yrs) and all living pts (9.5 yrs))
 * 98 pts XRT + immediate adjuvant goserelin, 75 pts XRT alone w/ delayed goserelin @ time of failure.
 * Conclusion : Multivariant analysis shows XRT + immediate adj goserelin have SS benefit in all four end points analyzed-- biochem control, met failure, DSF, absolute survival. Need prospective randomized trial to confirm, but until then, pN+ pts should be considered for XRT + immediate hormonal manipulation rather than XRT alone with hormone manipulation at the time of relapse.

 * (closed due to poor accrual ) RTOG 96-08 (1997-98)
 * Randomized node-positive pts to indefinite total androgen ablation vs total androgen ablation plus RT to the pelvis + prostate. 50.4 Gy to the pelvis (to L4/5 interspace) with boost to 68.4 - 70.2 Gy.

Hormonal Therapy Alone

 * EORTC 30846 - Randomized to immediate ADT vs delayed ADT; no treatment of the primary tumor
 * 234 pts with prostate cancer and nodal metastases. No treatment to the primary tumor was given. Pts randomized to early ADT vs delayed ADT. Non-inferiority trial
 * 2009 PMID 18823693 -- "Early versus delayed endocrine treatment of T2-T3 pN1-3 M0 prostate cancer without local treatment of the primary tumour: final results of European Organisation for the Research and Treatment of Cancer protocol 30846 after 13 years of follow-up (a randomised controlled trial)." (Schröder FH, Eur Urol. 2009 Jan;55(1):14-22.)
 * Median f/u 13 yr. Median duration of protocol ADT 2.7 yr (delayed) vs 3.2 yr (immediate).
 * 59.4% of pts died from PCa; 82.5% died overall. Median OS 6.1 yr (delayed) vs 7.6 yr (immediate) (HR 1.22), not signficant (non-inferiority not proven).
 * Conclusion: "After 13 years of follow-up, survival or PCa-specific survival between immediate and delayed ET appear similar, but the trial is underpowered to reach its goal of showing non-inferiority."


text:
Cookbook talk:Oatmeal Banana Waffle

Paraphrased from ISBN 0-8280-1071-4 by --Mdavis 16:24, 28 Jan 2005 (UTC)

license: Creative Commons - Attribution Share-Alike - https://creativecommons.org/licenses/by-sa/4.0/

title: Cookbook talk:Oatmeal Banana Waffle


text:
Category:Orange recipes

Recipes involving oranges.

title: Category:Orange recipes


text:
Category:Beer recipes

Food recipes involving beer.

title: Category:Beer recipes


text:
Category:Ice cream recipes

Recipes involving ice cream.

de:Kategorie:Kochbuch/ Eis

title: Category:Ice cream recipes


text:
Category:Muffin recipes

Muffins are individually-sized baked goods, made from a thick batter, and baked in a muffin tin, possibly lined with muffin liner. Muffins are similar to cupcakes, and are characterized by a mushroom-like "head" or "crown" which is formed when the cooking batter rises above the top of the muffin tin. Muffins are usually sweet, and often involve berries suspended in the batter. Though sweet, muffins are usually eaten at breakfast.

ko:분류:머핀 요리

title: Category:Muffin recipes


text:
Category:Oat recipes

Oats are a cereal often used in baking and to produce derivatives as oat milk.

title: Category:Oat recipes


text:
Category:Chili recipes

Recipes for chili, the typically meat and chile pepper based stew to which beans are sometimes added, although there are various vegetarian or vegan chili recipes. For other recipes with the peppers as a main ingredient, see Chile recipes.

title: Category:Chili recipes


text:
User talk:Larry Luther

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:30, 27 July 2005 (UTC)

Book of the month
Programming:Ada has been nominated on Book_of_the_month/September_2005_voting. Prehaps you would like to support our Nomination.

--Krischik 10:34, 2 August 2005 (UTC)

title: User talk:Larry Luther


text:
User talk:Physcher~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:31, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Physcher. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Physcher~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:36, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:22, 19 April 2015 (UTC)

title: User talk:Physcher~enwikibooks


text:
User talk:Seabrook

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:32, 27 July 2005 (UTC)

title: User talk:Seabrook


text:
User talk:Will Von Wizzlepig

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:35, 27 July 2005 (UTC)

title: User talk:Will Von Wizzlepig


text:
User talk:Thorpe

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:36, 27 July 2005 (UTC)

title: User talk:Thorpe


text:
User talk:Doom Of Doom

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:38, 27 July 2005 (UTC)

title: User talk:Doom Of Doom


text:
User talk:Eddio~enwikibooks

Do you realise that this is English Wikibooks? (Donovan|Geocachernemesis|Interact) 00:42, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Eddio. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Eddio~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:07, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:55, 19 April 2015 (UTC)

title: User talk:Eddio~enwikibooks


text:
User talk:Member~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:50, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Member. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Member~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:29, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:15, 19 April 2015 (UTC)

title: User talk:Member~enwikibooks


text:
User talk:Renffeh

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:51, 27 July 2005 (UTC)

title: User talk:Renffeh


text:
User talk:Transform~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:53, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Transform. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Transform~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:51, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:36, 19 April 2015 (UTC)

title: User talk:Transform~enwikibooks


text:
User talk:Nbgoku~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:55, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Nbgoku. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Nbgoku~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 23:32, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 05:17, 19 April 2015 (UTC)

title: User talk:Nbgoku~enwikibooks


text:
User talk:Bpeikes~enwikibooks

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:57, 27 July 2005 (UTC)

Your account will be renamed
Hello,

The developer team at Wikimedia is making some changes to how accounts work, as part of our on-going efforts to provide new and better tools for our users like cross-wiki notifications. These changes will mean you have the same account name everywhere. This will let us give you new features that will help you edit and discuss better, and allow more flexible user permissions for tools. One of the side-effects of this is that user accounts will now have to be unique across all 900 Wikimedia wikis. See the announcement for more information.

Unfortunately, your account clashes with another account also called Bpeikes. To make sure that both of you can use all Wikimedia projects in future, we have reserved the name Bpeikes~enwikibooks that only you will have. If you like it, you don't have to do anything. If you do not like it, you can pick out a different name.

Your account will still work as before, and you will be credited for all your edits made so far, but you will have to use the new account name when you log in.

Sorry for the inconvenience.

Yours, Keegan Peterzell Community Liaison, Wikimedia Foundation 22:59, 17 March 2015 (UTC)

Renamed
 This account has been renamed as part of single-user login finalisation. If you own this account you can |log in using your previous username and password for more information. If you do not like this account's new name, you can choose your own using this form after logging in: . -- Keegan (WMF) (talk) 04:42, 19 April 2015 (UTC)

title: User talk:Bpeikes~enwikibooks


text:
User talk:Nuttyguy20

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally. (Donovan|Geocachernemesis|Interact) 00:58, 27 July 2005 (UTC)

title: User talk:Nuttyguy20


text:
Marinette Aluminum Boat Maintenance

Contents

 * Why a Marinette?
 * /Boat Handling/
 * /Corrosion/
 * /Electrical/
 * /General Mechanical Info/
 * /Painting/
 * Reference books
 * /Ventilation/
 * /Rules of the Road/
 * /Engine and Transmission/

title: Marinette Aluminum Boat Maintenance


text:
Marinette Aluminum Boat Maintenance/Corrosion

 * /Galvanic Corrosion Basics/
 * /Capac Monitors/
 * /Hazards/

Prevention

 * /Sealloy Zinc Anodes/
 * /Guppies/
 * /Magnesium Anodes/
 * /Isolation Techniques/


text:
Marinette Aluminum Boat Maintenance/Rules of the Road

Do sailboats have the right of way?

Navigation Rules at USCG

COLREGS

USCG on USE OF "NOT UNDER COMMAND" (NUC) SIGNALS


text:
Marinette Aluminum Boat Maintenance/Electrical

 * /Alternators/
 * /AC Wiring/
 * /Load Centers/
 * /Isolation Transformers/
 * /Battery Chargers/
 * /DC Wiring/
 * /Breakers and Fuses/
 * /Starting Circuits/
 * /Illumination/


text:
Marinette Aluminum Boat Maintenance/Electrical/Starting Circuits

The problem
The boat is a 37 aft cabin, with twin 440 Chryslers. I tried to start the engines (just to make sure they start) and the STBD engine won't turn over. If I use the parallel switch, it starts fine. Worked fine all summer up to now (mid-July).

I am not certain of how my three batteries are arranged--haven't had to worry about it until now. I have two batteries behind the STBD engine and one battery behind the PORT engine. For this discussion, we can ignore the port battery.

I disconnected the outboard battery behind the STBD engine--completely--NO wires connected to it. Had my wife try the STBD engine, and it turned over normally. So, obviously, the battery I disconnected is not the STBD starting battery. However, when it is connected, I cannot start the STBD engine without using the parallel switch...almost. Immediately after re-connecting the previously disconnected battery, I flipped the starter toggle and the STBD engine turned over. I fliped the switch off, then on again--nothing, except some buzzing from under the black cover with red reset switches on it that is mounted on the engine (don't know what it is called). No way to turn over the STBD engine without using the parallel switch.

I am wishing I had my wife try several times with the aforementioned battery disconnected to see what happened with multiple attempts, but we were rushed for time and had to get home, so now I have all night to ponder this problem.

Batteries were (so I am told by previous owner) brand new last season. Water covers the plates in all the batteries. The battery I disconnected reads 13.56 VDC.

Possible answers
Your batteries are probably arranged with two batteries on the STB connect in parallel (12.5 volts) The port bank is a single starting battery. On most Marinettes the majority of the load is on the stbd bank of batteries. At least on my the factory wiring has almost everything but one bilge pump.. nav. lights and port starting on the STB bank. It varies depending on age.. configuration and what might have been added over the years.

The problem with having 2 batteries tied together in parallel is that the bank is only as good as the weakest battery. A bad cell for example will draw amperage from the good battery and pull them both down. Charging is the opposite.. the highest voltage battery will tell your regulator to shut down.

Assuming the STB will start without parallel switch with only one battery connected on the STB bank, it sounds like a bad battery. A bad battery could easily read 13.5 volts after being energized by the alternator but will have no reserve cranking capacity and will pull down quickly dragging the other battery down with it. Generally a good battery will hold a static charge of approx 12.5 volts at rest. A battery tester is the best way to test the capacity. The buzzing at the solenoid is low voltage caused by high current draw. Also check your wires under the black plastic cover at the solenoid. The wires often work loose. Make sure Contacts are clean and all wires are secure on the lugs. Do not knock off the yellow wire.. it is easy to do and it is your neutral disconnect switch.. if it falls off you will not be able to turn engine over at all.

For information I added a 4th battery to my Port bank using a ACR switch. This switch is sophisticated combiner switch. It allows current to flow into the 4th battery when charging at 13.6 volts or more. When voltage drops below.. (like when engines are off) it disconnects the 4th battery and holds it safe from discharge. You can over-ride it by flipping a switch.

The simple solution
The terminal connection (a multiple-type fitting with multiple leads on it) was loose, corroded and dirty on the positive side of the inboard-starboard battery. Cleaned connection with wire brush, tightened clamp fitting, and like magic, the problem was solved.


text:
Ordinary Differential Equations/Substitution 4

1)

$$y'=csc(x+y)-1$$

$$v=x+y$$

$$v'=1+y'$$

$$v'-1=csc(v)-1$$

$$sin(v)dv=dx$$

$$\int sin(v)dv=\int dx$$

$$-cos(v)=x+C$$

$$-cos(x+y)=x+C$$

$$y=arccos(-x+C)-x$$

2)

$$y'=csc(\frac{y}{x})+\frac{y}{x}$$

$$v=\frac{y}{x}$$

$$v'x+v=y'$$

$$v'x+v=csc(v)+v$$

$$v'x=csc(v)$$

$$sin(v)dv=\frac{dx}{x}$$

$$\int sin(v)dv=\int \frac{dx}{x}$$

$$-cos(v)=ln(x)+C$$

$$-cos(\frac{y}{x})=ln(x)+C$$

$$y=x arccos(-ln(x)+C)$$

3)

$$ycos(y^2)y'-sin(y^2)=0$$

$$v=sin(y^2)$$

$$v'=2yy'cos(y^2)$$

$$\frac{v'}{2}-v=0$$

$$v'=2v$$

$$\frac{dv}{v}=2dx$$

$$\int \frac{dv}{v}=\int 2dx$$

$$ln(v)=2x+C$$

$$v=Ce^{2x}$$

$$sin(y^2)=Ce^{2x}$$

$$y^2=arcsin(Ce^{2x})$$

4)

$$y'=yln(y)+y$$

$$v=ln(y)$$

$$v'=\frac{y'}{y}$$

$$v'y=yv+y$$

$$v'=v+1$$

$$\frac{dv}{v+1}=dx$$

$$\int \frac{dv}{v+1}=\int dx$$

$$ln(v+1)=x+C$$

$$v+1=Ce^x$$

$$v=Ce^x-1$$

$$ln(y)=Ce^x-1$$

$$y=e^{Ce^x-1}$$

5)

$$y'=(x^2+y-1)^2-2x$$

$$v=x^2+y-1$$

$$v'=2x+y'$$

$$2x+y'=(x^2+y-1)^2$$

$$v'=v^2$$

$$\frac{dv}{v^2}=dx$$

$$\int \frac{dv}{v^2}=\int dx$$

$$-\frac{1}{v}=x+C$$

$$v=\frac{-1}{x+C}$$

$$x^2+y-1=\frac{-1}{x+C}$$

$$y=\frac{-1}{x+C}-x^2+1$$

6)

$$y'=\frac{x^2}{y^2}+\frac{y}{x}$$

$$v=\frac{y}{x}$$

$$y'=v+xv'$$

$$v+xv'=\frac{1}{v^2}+v$$

$$v^2dv=\frac{dx}{x}$$

$$\int v^2dv=\int \frac{dx}{x}$$

$$\frac{1}{3}v^3=ln(x)+C$$

$$\frac{y^3}{3x^3}=ln(x)+C$$

$$y=(3x^3(ln(x)+C))^{\frac{1}{3}}$$


text:
Ordinary Differential Equations/Substitution 3

Solve the following differential equations via substitution methods. For some, you will have to come up with your own method.

1) $$y'=csc(x+y)-1$$

2) $$y'=csc(\frac{y}{x})+\frac{y}{x}$$

3) $$ycos(y^2)y'-sin(y^2)=0$$

4) $$y'=yln(y)+y$$

5) $$y'=(x^2+y-1)^2-2x$$

6) $$y'=\frac{x^2}{y^2}+\frac{y}{x}$$


text:
User talk:68.238.160.43

Come introduce yourself at the new users page. If you have any questions, you can ask there or contact me personally.

PS: A better way to name the pages of your book is to add sub pages with a slash (e.g.,Marinette aluminum boat maintenance/Corrosion, that automatically adds a link back to the main page (you can also use a colon, that doesn't add a back link). You can easily rename your existing sub pages by clicking on the move tab at the top of the page (you can also use it to fix spelling mistakes, like aluminium). Renaming like that also ensures that your book conforms to Wikibook's policy, and that you don't have name collisions with other books. (Donovan|Geocachernemesis|Interact) 04:38, 27 July 2005 (UTC)

title: User talk:68.238.160.43


text:
Making an Island/Facilities/Communication

Shortwave Radio: assuming your island now has power or batteries that can run a shortwave radio this would be your best option for communication.

Communications
Communications can be split into two general areas, data and voice.

External Communications
Voice

Tying into the worldwide telephone network is not difficult even if out at sea. There are a number of satellite networks designed for just this purpose. However due to the geosynchronous nature of most of the satellites used they have a problem covering the poles. The main exception to this is the iridium system which uses many polar orbiting satellites to provide full coverage of the world. However if we have a data connection using satellite then it is not necessary to use voice channels over the satellite as it can all be provided via VoIP. If we are close enough to land we may even be able to lay fiber optic cables out to the island, thus providing much more bandwidth than any satellite ever could for a much lower cost.

Data

What has just been said about voice communication can equally be said about data networks.

Internal communications
As voice communications can be digitized easily and carried over a data network in makes sense only running one type of communication network throughout. There are many options for this, the cheapest solution would be to leverage standard commercial hardware for the purpose. This boils down to 3 media types and a handful of standards. The media types are radio, fiber and cable. Each of these has advantages and disadvantages. Radio is very cheap to install but has problems with interference, range and lack of bandwidth. Cable, meaning Gigabit Ethernet in this case also has a range problem unless routers are used but has quite a lot of bandwidth and more can be added by just running an extra cable. Fiber is the most expensive to install but has fewer limits of range (few km for multi mode fiber and around 80km for single mode fiber) and has a lot of scope for upgrading bandwidth (WDM can be used to send multiple signals down a single pair).


text:
Portuguese/Present subjunctive tense irregular verbs

Most verbs which are irregular in the present tense can be made into the present subjunctive by removing the "o" from the first person present indicative

FAZER Eu faço (present indicative) - faç

And then adding the appropriate endings:

FAZER (present subjunctive) Eu faça Tu faças Ele faça Nós façamos Vós façais Eles façam

However, there are some exceptions. The following verbs have irregular stems. The endings, however, are regular.

SER (to be)- eu seja

ESTAR (to be)- eu esteja

HAVER (to exist)- eu haja

SABER (to know)- eu saiba

QUERER (to will)- eu queira

TRAZER (to bring)- eu traga

TER (to have)- eu tenha

PÔR (to put down)- eu ponha

VER (to see)- eu veja

PODER (to be able)- eu possa

LER (to read)- eu leia

DIZER (to say)- eu diga

FAZER (to do)- eu faça

VIR (to come)- eu venha

HAVER (to have)- haja

OUVIR (to hear)- ouça

PERDER (to lose)- perca

The following verbs are completely irregular.

DAR (to give) Eu dê Tu dês Ele dê Nós dêmos Vós deis Eles dêem

And also

IR (to go) Eu vá Tu vás Ele vá Nós vamos Vós vades Eles vão


text:
Ada Programming/Attributes/'Valid

Description
Objects may become invalid via import, unchecked conversions, overlays, etc.

The Valid attribute can be used with an object of any scalar type (that is, numeric or enumeration types) to know whether its value is valid (e.g. not out-of-range, etc.). The result is always True or False; neither Constraint_Error nor any other exception are ever raised.

It is important that the evaluation of the attribute does not count as reading the object, whereas reading an invalid object makes the program erroneous.

Example
My_Enum (Value1, Value2, Value3); My_Enum (Value1 => 2, Value2 => 4, Value3 => 6 ); Result            : Natural; Enum_Var, Other_Var: My_Enum; Sneaky_Back_Door  : Integer; Enum_Var'Address Sneaky_Back_Door'Address; ...  Result' Result := Natural'; ; ... Sneaky_Back_Door := 1; Other_Var := Enum_Var; ...  Enum_Var' Enum_Var := My_Enum'; ;

Note that in the erroneous assignment statement above, no range check is performed (hence no exception will be raised) since both variables are of the same subtype.

Wikibook

 * Ada Programming
 * Ada Programming/Attributes

Ada Quality and Style Guide

 * — Consider using the 'Valid attribute to check the validity of scalar data.
 * — Use the 'Valid attribute to check the validity of scalar values obtained through Ada.Direct_IO and Ada.Sequential_IO.
 * — In the presence of the abort statement, consider using the 'Valid attribute to check the validity of scalar data.

Ada Rationale

|Valid

title: Ada Programming/Attributes/'Valid


text:
Template:Ada/95/R3

[http://www.adaic.org/standards/95rat/RAThtml/rat95-p-.html#- .. ] 95/R3

title: Template:Ada/95/R3


text:
Template:Ada/95/R2

[http://www.adaic.org/standards/95rat/RAThtml/rat95-p-.html#. ] 95/R2

title: Template:Ada/95/R2


text:
Template:Ada/95/R1

95/R1

title: Template:Ada/95/R1


text:
Talk:Puzzles/Lateral puzzles/5/Solution

An anonymous user added: "The room was located near a river, when the river flooded, the water level rose and lifted the man to the ceiling, leaving the floor flooded."

Firstly, the first sentence is sufficient cause by itself. It doesn't need the river flooding to happen as well. If this was meant to be an alternative solution, it should be marked as such, not made to look like a continuation of the story.

Secondly, should a river flood, can one in practice seize the opportunity to hang himself? -- Smjg 10:14, 27 July 2005 (UTC)

title: Talk:Puzzles/Lateral puzzles/5/Solution


text:
Portuguese/Imperfect subjunctive tense regular verbs

The imperfect subjunctive is formed by adding the following endings to the stem.

For all verbs this is formed from the  third person plural preterite stem plus the set endings in the table below for the type of verb

What is meant by the 'stem' in this case is what is left after taking the 'ram' ending from the 'eles' form of the preterite tense.

Trying this with a regular verb (1st person singular form): FALAR > falaram - ram = fala > fala + sse = FALASSE

Trying this with an irregular verb (1st person singular form): FAZER > fizeram - ram = fize > fize + sse = FIZESSE

For the 'nós' and 'vós' forms, accents must be added as per the table below:


text:
Portuguese/Personal infinitive

There are no exceptions or irregularities in the formation of the personal infinitive (except for the stem pôr, which drops the circumflex when expanded). All verbs are created as follows.

title: Portuguese/Personal infinitive


text:
Mythology/English Mythology

People In Myth and Legend

 * /King Arthur/ (WP)
 * /Robin Hood/ (WP)
 * /Lady Godiva/ (WP)
 * /Hereward the Wake/ (WP)
 * /Corineus/ (WP)
 * /Guy of Warwick/ (WP)

Dragon Myths

 * /St George and the Dragon/
 * /Lambton Worm/ (WP)
 * /Linton Worm/
 * /Longwitton Dragon/

Giants in Myth

 * /Gog and Magog/ (WP)
 * /Gogmagog/
 * /Cormoran and Cormelian/

Other Creatures

 * /Beast of Bodmin Moor/ (WP)
 * /Reynardine/ (WP)
 * There are many legends of /Phantom Black Dogs/
 * /The Memaid of Zennor/
 * /Pixies/
 * /Black Annis/ (WP)
 * /Spriggans/ (WP)
 * /Knockers/ (WP)
 * /Anthropophagi/ (WP)
 * /Redcap/ (WP)

Ghosts and Spirits

 * /Iannic-ann-ôd/ (WP)
 * /Herne the Hunter/ (WP)
 * /Will o' the Wisp/ (WP)
 * /Boggarts/ (WP)

title: Mythology/English Mythology


text:
Mythology/English Mythology/Phantom Black Dogs

Across Britain there are many accounts of phantom black dogs. The beasts are often said to be monstrous goblin-dogs with huge teeth and claws.

The name for these spectre-hounds vary from place to place:

 * The most famous is probably the Barghest of Yorkshire, a nocturnal beast who's appearance is regarded as an omen of death.
 * The Demon of Tedworth, the Black Dog of Winchester and the Padfoot of Wakefield all shared the characteristics of the Barghest of York.
 * In Lancashire the spectre-hound is called Trash or Striker.
 * In Cambridgeshire and on the Norfolk coast it is known as Black Shuck or Shock.
 * In the Isle of Man it is styled Mauthe Dog. People believe that anyone who sees the dog clearly will die soon after the encounter. It is mentioned by Sir Walter Scott in The Lay of the Last Minstrel--
 * "For he was speechless, ghastly, wan
 * Like him of whom the Story ran
 * Who spoke the spectre hound in Man."

 * In Jersey folklore, the Black Dog of Death is called the Tchico, but a related belief in the Tchian d'Bouôlé (Black Dog of Bouley) tells of a phantom dog whose appearance presages storms. The story is believed to have been encouraged by smugglers who wanted to discourage nocturnal movements by people who might witness the movement of contraband.
 * In Wales its counterpart was Gwyllgi, the Dog of Darkness, a frightful apparition of a mastiff with baleful breath and blazing red eyes. A Welsh variant is the Cwn Annwn, or dogs of hell.


text:
Latin/Lesson 3-Subjunctive Imperfect

The conjugation of the subjunctive imperfect active follows a simple rule. The verb in its infinitive form, that is, the second principle part, (amāre, to love, for example) simply has the active personal endings (-m/ō, -s, -t, -mus, -tis, -nt) added:

ego     amārem

tu      amārēs

is      amāret

nos     amārēmus

vos     amārētis

ei      amārent

the passive voice is formed by the addition of passive personal endings (-r, -ris (-re), -tur, -mur, -minī, -ntur) onto the infinitive stem

ego     amārer

tu      amārēris (-re)

is      amārētur

nos     amārēmur

vos     amārēmini

ei      amārentur

Application
The imperfect subjunctive is only used for complex syntactic constructions; cum clauses and indirect questions and the like. Rarely, if ever, does it stand alone.

Because/Cum
One application is in its use with 'cum' in the sense of 'because' as a clause. e.g.
 * Diutius cum sustinere nostrorum impetus non possent, Helvetii se in montem receperunt.:When(Because) the Helvetis could not sustain/resist our attacks for long, they retreated to the mountains.

title: Latin/Lesson 3-Subjunctive Imperfect


text:
User:Sansap

I have come to know about this extremely useful, facile and knowledgeable site only by my luck. I like to use this platform to talk about Languages and dialects of India. I belong to Madhya Pradesh and speak Hindi ,Marathi and English. there are some dialects i have been using and coming accross over here viz. MALWI, BUNDELKHANDI, NIMADI. people interested in these are welcome.

Retrieved from "http://en.wikibooks.org/wiki/User_talk:Sansap" --Sansap 15:17, 27 July 2005 (UTC)

title: User:Sansap


text:
User talk:24.176.210.199

Template:Computer Science bookshelf
Before you edit special pages you should think a litte:

 * 1) If you have inserted the stage today then the day inserted is not unknown.
 * 2) dead links are not allowed on Template:Computer Science bookshelf!
 * 3) no content is 0% not 25%

title: User talk:24.176.210.199


text:
General Anatomy/Nervous System

The nervous system of higher vertebrates including humans is a widely distributed communication and processing network that serves controlling functions over other organ systems, possesses a key function in the orientation of the individual, controls its behaviour, motor function, sensory processing and contains mechanisms to store information.

The structural unit of nervous system are neurons. Neuron is a kind of cell that specialises in conducting electric signals between portions of the body. All neurons have a body called a Soma. The Soma contains the nucleus and all of the other organelles that are needed to keep the cell alive and functioning. Neurons also have directionality to them. On one side of the neuron are the dendrites. You can think of this side as being the 'input' side. The dendrites are branching structures which connect with the outputs of other neurons. They typically spread over a wide area in the immediate vicinity of the neuron. This allows the neuron to get inputs from a number of different synapses. The other end is the 'output'. It contains an axon and ends in a number of synapses which usually connect to the dendrites of other neurons or are connected directly to muscles. The axon is usually quite long compared to the rest of the neuron. In fact, you have some neurons with axons that extend the entire length of the body.

A classification of the nervous system can be performed under different aspects, of which the anatomical compartmentalization of its components defines the classical approach. Two major divisions of nervous can be described: 1. The central nervous system (CNS) 2. The peripheral nervous system (PNS).

Another approach is based on the functional compartmentalization between somatic and Autonomic autonomic parts of the nervous system. Both CNS and PNS comprise somatic and autonomic components. The autonomic nervous system consists of sympathetic and parasympathetic systems.

The neurons exist in all compartmentalization of the nervous system.

Sub-modules

 * /Functional compartmentalization/
 * /Anatomical compartmentalization/

title: General Anatomy/Nervous System


text:
Super NES Programming/DMA tutorial

=What is DMA, and why do we need it= One of the main limitations of the Super NES (apart from the slow memory access times) is the main processor. As already stated in the text on the memory mapping page, this was mainly due to the fact that the CPU was supposed to be backward compatible, meaning that in the beginning the SNES was supposed to execute NES ROMs as well as SNES ROMs. For this, the CPU featured a so-called emulation mode.

The processor in the original Nintendo Entertainment System was a Ricoh 2A03 (NTSC) or Ricoh 2A07 (PAL), which was actually a toned-down 6502. It lacked the binary-coded-decimal number support (which, for a time, was used for floating-point numbers until the IEEE754 specification was published) of the 6502, but was otherwise compatible to the processor. The Super Nintendo Entertainment System was running on a Ricoh 5A22, basically an enhanced version of the 65816. This CPU featured the already mentioned emulation mode, which would be able to execute games the same way the NES did. Also, the SNES used the same methods of addressing more memory than the native register size of the CPU (16 bit) suggested by basically using the same methods as with the older NES (bank switching). Note that these methods can be used also with running in emulation mode. Both the 2A03 and the 5A22 had very similar clock speeds:

Note that the PAL versions always tend to be a tiny bit slower, as NTSC renders 60 (interleaved half-)frames per second, while PAL only renders 50.

The reason why this page until now covered more about the CPU specifications than about direct access memory - which it will do very soon - is to illustrate the small CPU advantage the SNES had compared to the NES. The SNES had 64 times more memory than the NES, but only 2.5 times more CPU power.

One problem that can slow down a CPU significantly (even in today's age) is copying information (bytes) from device A to device B. The CPU is considered to be always faster than the memory it stores the current state in, and waiting for the memory controller to fetch/set the designated byte range can waste several clocks in which - if the CPU is not out-of-order superscalar - totally blocks the execution of the current program (that is, the game's ROM). Needless to say that the several Ricohs were never meant to be that particular sort of CPU.

Direct memory access is a method whereby memory is dynamically copied to another location independently of the CPU. In any modern computer, DMA is an essential requirement. Relating to the SNES, DMA can be used to quickly copy tile and palette data to the video RAM (also called VRAM), which would otherwise be copied by the slow CPU. Knowledge of DMA is a requirement for creating larger SNES programs, so this tutorial will cover just that.

DMA is used for copying graphics data, such as 8x8 tiles and tile maps, to the VRAM, and palette data to the CGRAM. These locations can only be accessed by reading or writing to certain hardware registers repeatedly (for more information see the memory mapping and the hardware registers page).

=DMA in detail=

To understand the way DMA works, we will take a short look into how the SNES handles its memory.

The console basically has three buses which are connected with several devices within it. These three buses are:

 * 1) Bus A: a 24-bit-wide address bus, which handles the communication between the CPU, the cartridge (ROM + SRAM), and the main memory (WRAM) - this is the main bus.
 * 2) Bus B: an 8-bit-wide address bus, which may be used via special addresses in the main bus' address space (hardware registers) and which connects the APU (audio) and the PPUs (video) with it.
 * 3) an 8-bit-wide data bus, which is controlled by both address buses for sending the data to various locations. This bus is blocked for the CPU whenever you issue one or more DMA processes.

Note that the data bus is really just one byte wide, while the CPU is supplied with various 16-bit registers. That means that one 16-bit register can never be written or read in one bus' cycle clock, but only in two.

The CPU of the SNES contains a DMA controller which supports 8 DMA channels in total. This means that 8 processes of copying chunks from one device to another may be set up and started simultaneously. Each channel can be specifically configured to behave in a certain manner. The channels execute their program, while being the first channel (index 0) with the highest and the eighth channel (index 7) with the lowest priority.

DMA controllers in common PCs can be configured to perform the task they are assigned to in a specific way, which is also called "mode". Also, PC DMA controllers can be used for various other devices, like for all devices connected to the system bus (ISA, PCI, AGP, PCIe).

The SNES supports only one mode, "burst", which basically means that the CPU will halt completely as long as there is at least one DMA process which is not finished yet. The reason for this is that for the transfer both the CPU and the DMA controller use the system bus to communicate with the other devices, but only one device (the master device) can use the system bus at the same time – either the CPU or the controller (more modern controllers offer the opportunity to transfer tiny chunks of data and then give the control of the system bus back to the CPU, immediately requesting the system bus again, so that the CPU may finish its pending operations and then return control of the bus to the controller – or not, if the CPU has to perform lots of memory accesses). Also, the SNES controller can only communicate with either the APU or the PPUs.

The registers of the controller are exposed through the hardware registers from $4200 to $4400 in the system banks $00 – $3F and $80 – $BF. There is a main register which upon writing into will start all DMA transfers it was set to start. Successive registers will contain information for each channel on what the channel is supposed to do, when activated.

=HDMA=

While the normal DMA controller can copy the data it was programmed to only in "burst" mode, and this up to 64 KB (one entire bank), the SNES features another method to copy chunks to various devices, which is a little bit like PC DMA controllers work. This kind of DMA is called HDMA (Horizontal Direct Memory Access) and is executed only during H-blank (that is the time it takes for the beam laser to reset to the original position after drawing a line). Since this time span is very very small, only 1 to 4 bytes can be transfered during one H-blank.

=DMA registers=

Note: x is the index of the channel (indexed by 0 to 7). So basically, 16 bytes of address space are reserved for each channel.

 NOTE: This tutorial is incomplete and untested.

NOTE: A DMA channel's transfer size, when set to #$0000, is read as a transfer of 65536 bytes, not 0 bytes.

=some code=

Loading Palettes
Here is a macro for loading a palette data into the CGRAM(the place where palettes are stored):

Loading VRAM
Here is a macro for loading a data into the VRAM(the place where tiles and tile maps are stored):

=External Links=
 * Information on the NES's CPU
 * The base processor the 2A03 was built from
 * The (in)famous IEEE754 specification
 * Informations on the SNES's CPU
 * The base processor the 5A22 was built from
 * The Von Neumann bottleneck, explained
 * What out-of-order execution means and why it is a good thing ... sometimes
 * How the CPU tries to execute one instruction for several parameters

=See Also=
 * SNES Memory Informations
 * SNES hardware registers

title: Super NES Programming/DMA tutorial


text:
ColdFusion Programming

ColdFusion is a JVM-based programming language that supports scripting and templating and was developed by J.J. Allaire in 1995 to make development of CGI scripts easier and faster. It has matured over the years to include many interfaces with other languages and environments.

ColdFusion History
Timeline: n language.
 * July 1995 - Cold Fusion 1.0 released.
 * November 1996 - Cold Fusion 2.0 released. This release included 150+ additional functions.
 * July 1997 - Cold Fusion 3.0 released. This release included custom tags.
 * November 1997 - Cold Fusion 3.1 and ColdFusion Studio Released. ColdFusion Studio was the first editor specifically designed to work with ColdFusion.
 * November 1998 - ColdFusion 4.0 released. This is the first release where Cold and Fusion were combined without the space.
 * August 1999 - ColdFusion 4.5 released. This was the first time that a true debugger was included.
 * March 2001 - Macromedia bought Allaire including the ColdFusio*June 2001 - ColdFusion 5.0 released. This release included the cfgraph functions.
 * June 2002 - ColdFusion MX (6) released. This release was a complete rewrite to a Java Engine.
 * August 2003 - ColdFusion MX 6.1 released. This was bundled with JRUN.
 * February 2005 - ColdFusion MX 7 released. This included Rich Internet Application Support.
 * December 2005 - Adobe merged with Macromedia.
 * July 2007 - ColdFusion 8 released.
 * October 2009 - ColdFusion 9 released.
 * May 2012 - ColdFusion 10 released.
 * April 2014 - ColdFusion 11 released.
 * 2016 Release
 * 2018 Release
 * 2021 Release

ColdFusion servers prior to version 6.0 were written in C++.

Since version 6.0, the ColdFusion application server is a Java application sitting on top of the Java Platform. When a page is first called, the ColdFusion code is converted into Java bytecode; this allows better integration with the Java platform and also allows JSP "Java server pages" to be called and run from within a ColdFusion application.

Beginning in version 7 there was a dramatic focus on RIA (Rich Internet Applications). The ability to include flash forms, xhtml forms, dynamically created pdfs and flashpaper were all included.

Version 8, released in mid 2007, showed dramatic performance improvements, and extended the language functionality to include image processing, presentations, MS Exchange integration, support for .Net components, PDF Form manipulation, Ajax form components (based upon ExtJs 1.1), and more.

Version 9 was released in October 2009, providing many huge advancements to the server and the language. Almost all ColdFusion tags now have CFScript equivalents, allowing developers to 'script' entire applications. New integration points now include Hibernate ORM (built-in), index and search from either Solr (new) or Verity, MS Office/OpenOffice document manipulation (presentations, spreadsheets and documents), and MS Sharepoint integration. There is also an AIR based desktop application, which can be used to administer/update multiple server instances remotely, and a brand new, Eclipse based IDE (ColdFusion Builder) is currently in public beta testing. Further scripting capabilities include enhancements to the ColdFusion JavaScript functions, used for interaction with the ColdFusion Ajax components (now upgraded to ExtJs 3.x), as well as support for Server-Side ActionScript, and a complete ActionScript include library to tap into core ColdFusion services (primarily for Flex integration). Adobe is also in closed beta testing of a new Amazon EC2 instance offering, and has adjusted it's licensing to include cloud computing and VPS deployment scenarios.

Today there are several ColdFusion Application servers (compilers), the most popular is the Adobe ColdFusion server. Other popular options include the open source Railo (a project under JBoss) and OpenBD (NewAtlanta), as well as the enterprise BlueDragon (NewAtlanta), which is built on .Net.

ColdFusion web pages make up around 10% of the web; its success is due to its simplicity and small learning curve. The majority of ColdFusion Developers started off as HTML designers, Due to CFML "ColdFusion Markup Language" being a Tag based language it looks very similar to HTML, which makes it very attractive to HTML coders with very little programming experience

ColdFusion Advantages
ColdFusion today offers Java developers a faster and more effective way to develop web based applications, as an application written in the ColdFusion language will generally require a lot less code than a Java application. The advantage here is that Java developers can still call all their pre-existing Java objects from within a ColdFusion application.

Less advanced developers who have no experience with Java can use ColdFusion without ever having to know any Java. Highly trained programmers can develop web programs, including Internet and intranet programs, in a much shorter time.

Developer Community
ColdFusion has had a long history of developer support including Team Macromedia and Coldfusion/Macromedia/Adobe User Groups.

Timeline:
 * July 1996 - Washington DC Cold Fusion users group is formed.
 * October 1999 - DevCon is held in Boston, MA.
 * November 2000 - Devcon is held in Washington, DC. Election results were made available via big screen at the Social Events.
 * October 2001 - DevCon is held in Orlando, FL.
 * November 2002 - MAX conference is held in Orlando, FL.
 * November 2003 - MAX conference in Salt Lake City, UT.
 * June 2004 - Ben Forta, Coldfusion's Product Evangilist, demos Blackstone (version 7) to 20 user groups around the world.
 * November 2004 - MAX conference in New Orleans, LA.
 * October 2005 - MAX conference in Anaheim, CA.
 * October 2006 - MAX conference in Las Vegas, NV.
 * April, May 2007 - Coldfusion on tour, demoing Scorpio (version 8) to user groups.
 * September, October 2007 - MAX conference in Chicago, IL.
 * November 2008 - MAX conference in San Francisco, CA.
 * October 2009 - MAX conference in Los Angeles, CA.

Additionally there have been numerous CFUN/CFUnited conferences held usually in Maryland around June of each year.

Table of Contents

 * /variables/
 * CFSET
 * CFOUTPUT and Pound signs
 * Evaluate
 * Variable Lookup

 * /databases/
 * Setting up Datasources
 * CFQuery
 * CFInsert
 * CFUpdate
 * Grouping Query Displays
 * Query of Queries

 * /data structures/
 * Lists
 * Arrays
 * Structures
 * Queries
 * CFDUMP

 * /control structures/
 * CFIF
 * CFSWITCH
 * CFLOOP

 * /dates/
 * Creating dates
 * Displaying dates
 * Modifying dates

title: ColdFusion Programming


text:
Dutch/Lesson 9

Intermediate level
Welcome to the first cycle of the intermediate level! This level will concentrate on building more complicated sentences using modal and auxiliary verbs, separable verbs and dependent clauses. That means that there is more grammar to cover but also that syntax -word order- will start to play a more important role, because you will learn to form more complicated sentences.

Future
The official future tense is formed using the auxiliary zullen + the infinitive

In Dutch this tense is called: de onvoltooid tegenwoordige toekomstige tijd (ottt), the imperfect present future tense. We shall revisit this nomenclature later.

 * ik vind - I find.
 * ik zal vinden - I'll find.

But you can also express the future by using a present, if futurity is declared in the sentence by an adverb (like 'tomorrow').

 * ik vind het wel - I find it.
 * ik zal het vinden - I'll find it.
 * ik vind het morgen wel - I'll find it tomorrow

Occasionally, Dutch resorts to the use of gaan:

 * dat gaat twee weken kosten - that is going to take two weeks.

In both cases the infinitive ends up at the end of the sentence.:

 * je het op de derde verdieping  - you  it on the fourth floor.

Zullen is an irregular verb (It is the cognate of shall):

Conditional or Future-in-past
Its past tense forms what it known as the onvoltooid verleden toekomstige tijd (ovtt), "the imperfect past future tense" that roughly corresponds to the conditional tense in English.

 * ik zeg - I say
 * ik zou zeggen - I would say

This tense is also used to express a future tense within the framework of a past narrative:

 * Hij zal komen
 * Hij zegt dat hij zal komen
 * Hij zei gisteren dat hij zou komen - He said yesterday: "I will come"

Infinitives instead of participles. Modal verbs
The verb zullen does not have a past participle, instead its infinitive is used in phrases like:

 * Ja, ik heb dat zullen doen, maar ik had geen tijd meer.
 * Yes I had intended to do so, but I ran out of time

Kunnen
There is a number of verbs that show this phenomenon, particularly the modal verbs. A good example is kunnen (can) although this verb does have a past participle and it can be used in separation:

 * ik kan dat niet - I cannot do that
 * ik heb dat nooit gekund - I have never been able to.
 * ik heb dat nooit kunnen doen - I have never been able to do that.

Sometimes this leads to lengthy strings of infinitives:

 * waar ik het zou hebben kunnen laten verlengen.
 * where I would have been able to have it extended.

Kunnen is an irregular verb as we have seen before. Its past tense is:

 * ik, jij, hij kon
 * wij, jullie, zij konden (could)

 * hij kon niet meer - he was exhausted (lit. he could no more)

Mogen
Mogen usually translates into may or to be allowed to, to be permitted. It too is irregular. Its primitive tenses are irregular:

 * mogen - mocht - gemogen, gemocht or gemoogd

In addition the present tense is:
 * ik mag
 * jij mag, u mag, gij moogt
 * hij mag
 * wij, jullie, zij mogen

 * Mag ik een kopje thee - May I have a cup of tea?
 * Je mag niet jokken! - You're not allowed to fib!

The perfect participle is only used when no other verb follows:

 * Hij heeft dat nooit gemogen - He has never been permitted that

Otherwise it is replaced by its infinitive:

 * Hij heeft dat nooit mogen doen. - He has never been permitted to do that.

Moeten
The English defective verb must is originally the past tense of a verb mote and Dutch both cognates (moet and moest) are still in use. The primitives are irregular:

 * moeten - moest -gemoeten

but otherwise the verb is regular. It means must or to have to

 * Ik moet vanavond werken - I have to work tonight.
 * Ik moet weg! - I got to go!

Its participle also often is replaced:

 * Hij heeft moeten werken - He has had to work.

Hoeven
This came from a similar word as the English behove

The primitives are mixed: hoeven - hoefde - gehoeven

This verb means need to, must but it is only used either in the negative:
 * Wij hoeven ons paspoort niet te verlengen -- We do not need to have our passport extenden

Or, with a limitation like only
 * Wij hoefden alleen maar een brief te sturen -- We only needed to send a letter.

Notice that it is followed by the extended infinitive' with the preposition te

Again the participle can be replaced by an infinitive:
 * Je had dat niet hoeven doen -- You did not need to do that.

In that case the extension te is dropped.

Laten
The verb laten corresponds to the English verb to let but is used somewhat differently. It is a regular strong verb:

 * Laat mij maar rijden - just let me drive
 * Dat zul je laten! - no, you won't!
 * Ik heb het zo gelaten - I left it the way it was
 * Hij liet zich niet kisten - He fought back. (lit. he did not let himself be put in a coffin.)
 * Iets laten maken - Have something fixed.
 * Laat maar! - Don't bother!
 * Hij kan het roken niet laten - He can't stop smoking.

Stative verbs: staan, zitten, liggen, lopen
All of these are strong verbs:

Scholars do not agree whether to consider these verbs as auxiliaries or not. Some do consider them aspect auxiliaries, because they often serve to express continuity in combination with the infinitive of other verbs extended with the preposition te:

 * Ik zit te lezen - I am reading (while on my chair)
 * Ik loop te denken - I am thinking (while going somewhere)

These verbs also frequently replace to be in impersonal expressions with er:

 * Er liggen drie boeken op tafel - there are three books (lying) on the table
 * Er zitten nog drie koekjes in de doos - there are still three cookies (sitting) in the box
 * Er loopt een goeie film - there is a good movie on.

The perfect of these expressions drop the "te" and use an infinitive to replace the past participle:

 * Ik heb zitten denken - I have been thinking (on my chair)
 * We hebben staan bellen - We have been on the phone (while on our feet)

Other verbs taking the extended infinitive
There are other verbs that are followed by the extended infinitive but drop the extension te in the perfect or future tenses.

Recall: "Dat zou ik niet durven zeggen" - I would not dare to say that.

In the present tense durven - to dare does take the extension:

 * Ik durf te zeggen dat.. - I dare say that..

Other such groepsvormende werkwoorden - verb that form groups are:

 * beginnen - to begin
 * (be)horen, dienen - ought, to be expected
 * the modal verbs /copulas blijken, lijken, schijnen, heten, dunken

Doen: to do
As in English this verb is irregular.

Its role is more restricted than in English, but at times it can be used as an auxiliary that turns an ergative into an active construction:

 * Het vet stolt - the grease solidifies
 * De koude doet het vet stollen - the cold makes the grease solidify

Again the perfect has an infinitive:

 * De koude heeft het vet doen stollen. - the cold has made the grease solidify

Quizlet
The vocabulary of this lesson can be practiced at Quizlet (26 terms)

Progress made
Cumulative term count

 * Beginner level 1053
 * Les 9 27

 * Total number of terms 1080

title: Dutch/Lesson 9


text:
Cookbook talk:Gluten-Free

I added Chick Pea Flour, can someone please add specific details as to its baking/cooking properties? I don't know anything about its properties, I only have some food that is made from it. Thanks. --User:elysianfields 22:06, 27 July 2005 (UTC)

category
Category:Gluten-free recipes Ants Go Marching 17:14, 1 July 2006 (UTC)

More flours
Millet, quinoa and buckwheat are also worth adding to the gluten free flour lists. —Preceding unsigned comment added by 74.138.202.24 (discuss • contribs) 2008-03-01T01:10:02 in Administrative Assistance reading room.

title: Cookbook talk:Gluten-Free


text:
Category:Batter recipes

Recipes for multipurpose batters.

title: Category:Batter recipes


text:
Category:Herbs and spices

Herbs and Spices.

title: Category:Herbs and spices


text:
Software Engineers Handbook/Language Dictionary/Java

Java
Here is the Java wikipedia entry.

Type
Java is a full, procedural, object-oriented language.

General Syntax
The typical statement is completed by a semi-colon. For the assignment of b to a use:

Comments
Block comments are specified by a starting /* and ending */ They can span multiple lines.

Scope
Scope is defined by curly braces.

Conditional Statements
If and only if A is equal to B assign C to D, otherwise, assign E to F.

or

Alternatively, a switch statement can be used for multiple choice operations. This sample converts a number input to text.

Looping Statements
This code counts from 0 to 9, adding up the contents of the array.

This code repeats until the number 4 is found. If this runs off of the end of the array, there could be a problem.

This code increments the counter before the check is made, so that it starts with element 1.

Containers
Containers inherit from the Collection class. See the java.util package for specific containers including List, LinkedList, Queue, Stack, Dictionary and HashMap.

Algorithms
The Collection class has algorithms like sort.

Garbage collection
Garbage collection is automatic.

Physical Structure
Code is generally kept in files with a .java extension. It is compiled into Java byte code into files with .class extensions.

Tips
= // assignment == // comparison, is equal to Often using the one you don't want will compile, and will produce results you did not expect.
 * Classes in the Java packages are capitalized, methods are not.
 * Everything is a pointer. Use a clone method to avoid operating on the original element of a Collection.
 * Arrays start with index 0.
 * Don't confuse these two:

Web References

 * Java wikibooks page
 * The Sun java page has the API online as well as code examples.

Books and Articles
paper references here


text:
Radiation Oncology/GIST

Epidemiology
Rare. 0.1-3% of all GI tumors. But 20% of small bowel tumors. Incidence is 20 per 1,000,000 people / year. Predominantly affects those in their 5th - 7th decades.

Location: 60% from stomach, 30% from small intestine

Symptoms
GI bleeding is most common. Abdominal pain, bowel obstruction.

10% present with metastatic disease. Most common site of metastasis is to the liver. May spread to peritoneal surface.

Pathology
Term GIST was coined in 1983 by Mazur and Clark (PMID 6625048). GISTs were recognized as distinct tumors in the early 1990s, but the correct diagnosis of these tumors was problematic until around 2000.

Originate from the interstitial cell of Cajal, an intestinal pacemaker cell.

Previously were classified as visceral leiomyosarcomas due to their similar appearance histologically. Much of the older data for gastrointestinal sarcomas is therefore of little value because of the mixed histologies.

Immunohistochemistry: KIT (CD-117) positive, CD34 positive, smooth muscle actin variably positive. Negative for desmin. Usually negative for S100 (distinguishes from schwannomas).

Staging
Was added as a separate classification starting with the 7th edition of the AJCC Staging Manual. GISTs were not previously classified by the AJCC.

AJCC 7th Edition (2009) Primary Tumor
 * T1 - 2 cm or less
 * T2 - >2 cm and <= 5 cm
 * T3 - >5 cm and <= 10 cm
 * T4 - > 10 cm

Regional Lymph Nodes
 * N0 - no
 * N1 - yes (note: very rare in GIST)

Distant Metastasis
 * M0 - none
 * M1 - yes

Mitotic Rate
 * low - <= 5/50 HPF
 * high - > 5/50 HPF

Stage Grouping
 * For Gastric GISTs:
 * (includes omentum)

 * IA - T1-T2 N0, Low mitotic rate
 * IB - T3 N0, Low mitotic rate
 * II - T1-T2 N0, High mitotic rate; T4 N0, Low mitotic rate
 * IIIA - T3 N0, High mitotic rate
 * IIIB - T4 N0, High mitotic rate
 * IV - N1 or M1

 * For Small Intestinal GISTs:
 * (includes esophagus, colorectal, mesentery, and peritoneum)

 * I - T1-T2 N0, Low mitotic rate
 * II - T3 N0, Low mitotic rate
 * IIIA - T1 N0, High mitotic rate; T4 N0, Low mitotic rate
 * IIIB - T2-4 N0, High mitotic rate
 * IV - N1 or M1

Prognosis
Malignant potential depends on size and number of mitoses but can be difficult to predict in some cases. Are malignant in about 10-30% of cases.

NIH scale: (based on size and mitotic count) - PMID 12094370
 * Very low risk - < 2 cm, < 5/50 HPF
 * Low risk - 2-5 cm, < 5/50 HPF
 * Int risk - < 5 cm and 6-10/50 HPF, or 5-10 cm and < 5/50 HPF
 * High risk - any size and > 10/50 HPF, or > 10 cm and any mitotic count, or > 5 cm and >5/50 HPF

Major and minor criteria: - Bucher et al - PMID 15191872
 * Minor criteria: size > 5 cm, mitotic index >5 mitoses/50 HPF, necrosis, infiltration of adjacent structures, MiB1 index > 10%
 * Major criteria: LN invasion, metastases
 * Low risk - fewer than 4 minor criteria - 5-year survival is 95%
 * High risk - 1 major or 4 or more minor criteria - 5-year survival < 20%

c-KIT and Imatinib
Approximately 90% contain a mutation in the c-kit protooncogene which encodes the KIT receptor tyrosine kinase. The ligand for KIT is known as stem cell factor, Steel factor, or KIT ligand. The c-kit mutation is a gain-of-function mutation which provides a continuous signal for cell growth without the binding of the normal ligand and creates an antiapoptotic signal.

STI-571 or Imatinib (Gleevec) is a selective inhibitor of the ABL, BCR-ABL, KIT, and PDGF receptor tyrosine kinases. Usually given at a dose of 400-600 mg/day orally.

Treatment
Primary treatment is surgical resection.

Metastatic disease
Used in metastatic disease. Patients without c-kit mutations are less likely to respond.

Trials:
 * (Pending - trial closed in 2002) North American Sarcoma Intergroup study S0033 - tests Gleevec at 800 mg/d (divided BID) vs 400 mg/d (once daily) for metastatic GIST

 * EORTC trial - similar to Intergroup S0033

Duration of therapy:
 * French Sarcoma Group BFR14 (2002-)
 * Pts with metastatic GIST. After 3 yrs of Imatinib therapy, pts were randomized to continual therapy (C) vs interrupted therapy (I) with Imatinib. Pts on interrupted arm could resume Imatinib if progressive disease detected.
 * 2007 ASCO Abstract #10005 — "Continuous versus interruption of imatinib (IM) in responding patients with advanced GIST after three years of treatment: A prospective randomized phase III trial of the French Sarcoma Group."
 * 35 pts enrolled (19 interrupted vs 16 continuous). Median f/u 5.3 mos.
 * Higher rate of progressive disease in I pts. Reintroduction of Imatinib in the I arm after progression allowed tumor response (stable disease or overall response) in all pts.
 * Conclusion: high risk of rapid progression when treatment is interrupted.

Adjuvant therapy

 * Multicenter; 2012 PMID 22453568 Full Text -- "One vs three years of adjuvant imatinib for operable gastrointestinal stromal tumor: a randomized trial." (Joensuu, JAMA. 2012 Mar 28;307(12):1265-72.)
 * 400 high risk patients, defined by having at least 1 modified NIH Consensus Criteria
 * The longest tumor diameter >10.0 cm
 * Mitotic count >10 mitoses per 50 HPF
 * Tumor diameter >5.0 cm and mitotic count over 5
 * Tumor rupture before surgery or at surgery
 * Median follow-up 54 months.
 * 5yr RFS: 36-month group 65.6% vs 12-month group 47.9%
 * HR 0.46; 95% CI, 0.32-0.65; p < .001
 * 5yr OS 36-month group 92.0% vs 12-month group 81.7%
 * HR 0.45; 95% CI, 0.22-0.89; p = .02
 * Imatinib was generally well tolerated, but 12.6% and 25.8% of patients assigned to the 12- and 36-month groups, respectively, discontinued imatinib for a reason other than GIST recurrence.
 * Conclusion: Compared with 12 months of adjuvant imatinib, 36 months of imatinib improved RFS and overall survival of GIST patients with a high risk of GIST recurrence.

 * ACOSOG - adjuvant 400 mg/d x 1 yr after complete resection for high-risk (10 cm, tumor rupture, or multifocal). Compared with historical controls.

 * ACOSOG - Phase III, high-risk and moderate-risk (>3 cm). Randomized to placebo vs Imatinib x 1 yr.

Neoadjuvant

 * RTOG / American College of Radiology Imaging Network (ACRIN) - serial PET scans.

Radiotherapy
Poor response rate to RT. Only very scanty reports in literature. There have been case reports of RT being used as adjuvant therapy for positive margins and as primary therapy when combined with chemo and immunotherapy.

RT's role may be restricted to palliation: palliation for bleeding, pain

Review

 * 2007 PMID 17512858 -- "Gastrointestinal stromal tumour." (Rubin BP, Lancet. 2007 May 19;369(9574):1731-41.)

 * 2002 PMID 12094371 - Dematteo RP et al - Clinical management of gastrointestinal stromal tumors: before and after STI-571. 2002.

title: Radiation Oncology/GIST


text:
User talk:196.11.241.43

Please stop removing content from Wikibooks. It is considered vandalism. If you want to experiment, please use the sandbox. Thank you. (Donovan|Geocachernemesis|Interact) 23:27, 27 July 2005 (UTC)

title: User talk:196.11.241.43


text:
Category:Cobbler recipes

| Dessert | American Cuisine

A cobbler is an American fruit dessert which is usually made by placing fruit in a deep pot or casserole dish, mixing it with sugar and often a thickener such as corn starch, and covering with a biscuit or pastry crust.

title: Category:Cobbler recipes


text:
Category:Peanut recipes

Recipes involving peanuts.

title: Category:Peanut recipes


text:
Category:Basil recipes

Recipes involving basil.

title: Category:Basil recipes


text:
Category:Horse recipes

Recipes involving horse.

title: Category:Horse recipes


text:
Category:Curry recipes

 * For the ingredient, please see curry powder.

A Curry is a South and South East Asian dish, often made with curry powder or paste, which is generally a combination of vegetables and meat in a thickened and often spicy sauce.

title: Category:Curry recipes


text:
Category:Moroccan recipes

Recipes from Morocco.

title: Category:Moroccan recipes


text:
Category:Slovenian recipes

Recipes from Slovenia.

title: Category:Slovenian recipes


text:
Category:Chutney recipes

| South Asian cuisine |  United Kingdom cuisine |

Chutney was originally an Indian term for varieties of sweet or savory condiment spreads. Chutney can be made from fruits. vegetables, herbs, juices, milks or ferments, and is usually spicy, cooked, thick and slightly chunky. Depending on the recipe; salsas, relishes, pickles, dipping sauces and preserves might also be called chutneys.

Chutney is one of the food types spread around the world by British colonization. Vinegar was added to the recipe for English-style chutney. Vinegar is a preservative, giving autumn fruit a long shelf life. Indian pickles use | mustard oil as a pickling agent, but Anglo-Indian style chutney uses malt vinegar or  cidar vinegar which produce a milder flavor. Chutneys have a wide variety of forms. A common variant in Anglo-Indian cuisine uses a tart fruit such as tomato,  cidar  apples,  rhubarb or damson  plum pickle. In British culture mild chutneys are often eaten with hard cheese or with cold cuts of meat. (Rewritten from | Chutney on Wikipedia 2021-Jan).

title: Category:Chutney recipes


text:
Category:Scone recipes

Recipes for scones.

title: Category:Scone recipes


text:
Category:Nut and seed recipes

Recipes involving nuts.

title: Category:Nut and seed recipes


text:
Category:Salvadoran recipes

Recipes from El Salvador.

title: Category:Salvadoran recipes


text:
Category:Central American recipes

Recipes from Central America; geographically part of North America.

title: Category:Central American recipes


text:
Marinette Aluminum Boat Maintenance/General Mechanical Info

 * /Engine and Transmission/
 * /Hull/
 * /Railings/
 * /Rudder and Steering/
 * /Windows/
 * /References/


text:
Marinette Aluminum Boat Maintenance/Engine and Transmission

 * /Exhaust/
 * /Repowering/
 * /Shaft Alignment/
 * /Shaft Packing/
 * /Shaft Isolation/


text:
Template:An

[#fn_] /Templates

title: Template:An


text:
Template:Anb

⇧ /Templates

title: Template:Anb


text:
Making an Island/Construction Guides

Floating Fishnet
First of all, it would be better to construct these on land and then transport them to the water.

Materials:
 * Soil
 * Fishnets
 * Empty bottled water containers and/or empty drink bottles.
 * Make sure the bottles are closed and air tight; preferably plastic.
 * Do not employ glass bottles, they will break!

Here's how to calculate how many bottles you'd need for your island:
 * Calculate how much weight in soil you'll have for the island (in kilograms).
 * Calculate how much weight in other facilities you'll have for the island (in kilograms).
 * Calculate the maximum number of people you expect on the island, and multiply that number by 70 kg.
 * Add the above numbers, altogether, and add about an extra 5~15% of that for safety.
 * The resulting number is the total number of liters in bottles that you'll require. Divide the number by the bottle size (in litres) that you'll be using to get how many of them you need.
 * 250 mL = 0.25 L; 500 mL = 0.5 L

Steps:
 * 1) Spread the fishnet over a flat area where plants are able to grow into the soil but not the ground underneath (construct on top of something like concrete).
 * 2) Figure out how you want the empty bottles to lay in the fishnet.  You could try to tie them to the fishnet or just lay them on their sides (if you think the roots of the plants you're going to be using in the next step will secure them in the soil).
 * 3) Cover with soil and plant plants as hopefully they will trap the bottles in their roots. You will have to determine the depth of the soil you want. If it's too thin your weight won't be dispersed enough and you may fall through. If it's too thick it may simply sink.

Modular Construction
It is envisaged that the island will be produced in a modular way, with sections able to be added as required. Modules can be either free floating and anchored to the seabed, possibly using an existing sea mount as the anchor point, or built up from the seabed itself.

Modules can be any shape and design but the easiest shape both to deploy and built is the rectangular platform. Hexagon modules should also be considered for additional reasons. The prime one being increase of volume for a given surface area.

It is suggested that modules should be able to be raised and lowered in the water to allow the modules to be moved as needed. A module completely empty of water has less inertia and will be much easier to control for a tug or other propulsion system. A module half full of water for example will be much more stable as long as that water is prevented from moving from side to side (this is the same principle used for ship-board stabilizers and fuel tanks in cars.) The easiest way to do this is to provide baffles in the buoyancy tanks that prevent fluids from moving from one side of the tank to another.

One design that may be viable is that of a box, solid at all sides except the base which will be covered with either mesh, if an internal lift bag is to be used or solid of all sides with valves able to control airflow into and out of the tank. It is suggested that the tank be divided into several sections to allow for redundancy if a tank should become damaged. It is also suggested that the valves should be designed in such a way that if they fail there is a backup valve able to stop it failing in a dangerous way.

The biggest risk for any island is the destructive force of a storm. A floating island as suggested above should be able to cope with such a storm by increasing the amount of water in it buoyancy tanks. In doing so it will become heavier and sit lower in the water. It will also have less cross-sectional surface area to be pushed against by the wind. The only real problem will be the waves. Wave energy decreases with the depth below the surface. The depth being dependent on the wavelength of the wave. In calmer water the sub-surface effects of waves will be minimal, but during a storm wave-length increases and therefore sub-surface effects do also.

One possibility for a floating island which will be difficult in practice would be to literally sink the island during a storm and re-float it after it has passed. This would probably be a last resort option as it would require a lot of disruption unless the modules were designed for this action.

Compartmentalization of the buoyancy tanks of a module should allow greater tolerance of water ingress by limiting center of gravity shifts through the structure and thus making the module more stable. This can be proved in a little thought experiment. If we have a spherical module, unlikely but it makes it easier to demonstrate the basic idea, with 25% of its volume filled with water. Then there is nothing to stop the whole module from spinning in any direction about its center of gravity. If we now divide this sphere into many little compartments and fill the lowest 25% of these with water then we essentially have a module that bears a close resemblance to a weeble in terms of mass distribution. Each time it is pushed from its stable position it will tend to return to this equilibrium point. This is called pendulum stability. For every subdivision we create inside the module we have a set of trade offs. With every division we tend to the ideal module with a fixed center of gravity, but its a case of diminishing returns since while initial divisions will have great effect as you keep adding more you will reduce the effect and add more mass to the structure, also cutting down usable buoyancy tank volume. This isn't very scientific but instinct tells me that the ideal number of subdivisions is between 3 and 5 giving us somewhere between 9 and 25 separate buoyancy tanks, but this will depend upon application.

We will go through a worked example for the rough design of a cubic floating module.

If we require a rectangular module that has a surface of 5 meters by 5 meters and can take a payload of 4 tons in addition to its own mass then we need to calculate the mass of the structure, the mass of the water inside the structure and how much water we need to displace to get it to float.

The volume of the structure is given by the height x width x length for a rectangular object. We'll use the height as 3 meters for now, we can always go back and change it later.

This gives us a volume of 75m3.

If we assume that we will be using seacrete or concrete as a basis for the structure then the calculations are as follows. Steps will be similar but with different figures for other materials.

If we use a wall thickness of 0.1 meters then the volume of the walls is given by (height x width x thickness x 2) + (width x length x thickness x2) + (height x length x thickness x 2)

or

(3x5x0.1x2) + (5x5x0.1x2) + (3x5x0.1x2) = volume 3      +      5      +      3       = 11m3

The mass of the walls will be given by volume of walls x density

If we use the mass of sea water as 1020kg/m3, air as 1kg/m3 and concrete as 2750kg/m3

For concrete this would be

11 x 2750kg/m3 = 30250kg

If we add to this the mass of air inside the structure we get an overall figure of 30325kg

The volume of water the structure will displace if fully submerged is 75m3 (The volume inside the structure) + 11m3 (The volume of the walls) for a total of 86m3 The mass of water it will displace is 86m3 x density of water

or 86m3 x 1020kg/m3 = 87720kg

Since this is greater than the mass of the structure it should float and should be able to take a payload of 57395kg before it would begin to sink. However unless you distributed the load carefully the structure is more likely to fail before you get to this point.

So far we have neglected to include subdivision of the tanks into the calculations. If we wish to calculate the extra mass required to subdivide the buoyancy tanks we do the following.

Decide how much we will subdivide then tank by.

For example to divide it into 9 sub-tanks we would require 4 extra panels. 2 in the lengthwise direction and 2 in the widthwise direction. Volume of these panels can be calculated as follows.

(w x h x thickness x #panels) + (l x h x thickness x #panels) = total additional volume. for our example previously this would give an additional 6m3 of volume (which needs to also come off the usable volume of the tanks when filled with air) which has a mass of 6m3 x 2750kg/m3 = 16500kg

We can do this technique for more complex structures as long as the masses of the structure and water displaced is known or can be calculated.

Anchors
There are many techniques used for anchoring items to the sea bed. The simplest technique is simply to drop a large mass onto the sea bed and tether an object to it. However, this solution is neither a particularly elegant solution nor is it efficient in terms of raw materials.

One technique, which has gained popularity with structural designers in recent years, is the idea of dropping a large bell onto the sea floor and pumping water from it. While water is being removed, the bell will fill with sand, either by sucking up a large mass of sand into itself, thereby causing its mass to increase, or by burying itself in the seabed, causing an increase in static friction of the anchor. Which condition occurs will depend upon the design of the anchor and the amount of suction provided upon installation. It is unknown whether the first situation would have long term durability.

Biorock
The first step is to build a steel frame out of metal. (sources of metal can be rebar, thick gauge wire, tie wire, chicken wire, hardware cloth etc.) To create solid structures, the spacing between terminals should be kept to a minimum. (The reef structures currently being built feature spacing of half a foot or more) 1/4 to 1/2 inch might prove most advantageous for an island. Keep the anodes (positive terminal) around 4-6 inches away from the cathode (negative terminal) screen. the metal structure can be anchored in a shallow part of the ocean, powered by floating solar panels. Placing the anodes half a foot from the sides of the island the limestone will grow around the outside then later the insides will fill in. To increase the size, the anodes will be moved farther from the sides of the island.

title: Making an Island/Construction Guides


text:
Marinette Aluminum Boat Maintenance/References

Recommended books:

 * 1) Boatowner's Mechanical & Electrical Manual: How to Maintain, Repair, and Improve Your Boat's Essential Systems by Nigel Calder, 1995
 * 2) Powerboater's Guide to Electrical Systems: Maintenance, Troubleshooting, and Improvements by Ed Sherman, 2000
 * 3) Nigel Calder's Cruising Handbook: A Compendium for Coastal and Offshore Sailors 2001
 * 4) The Complete Guide to Metal Boats: Building, Maintenance, and Repair by Bruce Roberts-Goodson, 2000


text:
User talk:222.153.87.34

--Laura Scudder | Talk 03:31, 28 July 2005 (UTC)

title: User talk:222.153.87.34


text:
User:Psanand

Hi I am Anand. Iam working as a test engineer.

title: User:Psanand


text:
Making an Island/Moving a Floating Island

Towing
You could have a fleet of tugboats with cables attached to a sturdy part of your island tow it to another location.

If the design is modular the modules can be moved individually, in fact they could be linked in a long chain to minimize drag for travel over long distance and then rearranged on location.

Sails
Build a mast near the middle of your island so that you can use sails to drag your island to another location using wind. It's important that your mast is sturdy and large enough to catch enough wind to efficiently move your island, but not so big and heavy that its hard for your island to support it. Also, putting your sails too high might tip your island altogether in rough winds, so it is best to set it such that it is low enough not to let the island blow over (closer to the center of gravity), yet not so low that it gets in the way and/or is not able to catch enough wind. Making the bottom of your island more stream-line would help in reducing drag. This method should be more effective if your island is small.