text:
User:Williamtreseder

I'm a United States Marine and Stanford University graduate. Most of what I learned about writing and editing came from my mother, a former teacher and Phi Beta Kappa graduate from UC Berkeley. The love of learning and desire to share knowledge came from my father, another Stanford University alumnus who helped me get the library on a regular basis as a child, and regularly engages me in discussions now that I'm an adult.

I'm very passionate about veteran support organizations, and work for one - Taking Point based out of Scottsdale, Arizona.

title: User:Williamtreseder


text:
Doug Cunningham (politician)

Doug Cunningham (born October 13, 1954, in Osmond, Nebraska) is a politician from the U.S. state of Nebraska. He served in the Nebraska Legislature from 2001 to 2007.

Cunningham graduated from Wausa High School in 1972.

He was elected in 2000 to represent the 18th Nebraska Legislative District. In redistricting following the 2000 U.S. census, Wausa became part of the 40th District. Cunningham was elected to the 40th District seat in 2002.

In the legislature, he chaired the Business and Labor Committee, and sat on the Agriculture Committee and the Health and Human Services Committee.

source: wikimedia

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

title: Doug Cunningham (politician)


text:
Talk:Emergency Contact

I wonder if this page should redirect to Emergency management and we should use Emergency Contact (Will & Grace) for the television episode. --- Another Believer ( Talk ) 22:01, 22 September 2017 (UTC) Thoughts? Emergency management mentions 'emergency contact information' a few times and most people probably have this in mind when searching "emergency contact". --- Another Believer ( Talk ) 22:01, 22 September 2017 (UTC)
 * Honestly, I think this should be a disambiguation page. ToThAc (talk) 22:27, 22 September 2017 (UTC)
 * Agreed. --- Another Believer ( Talk ) 22:28, 22 September 2017 (UTC)
 * I converted the page and added a few links, but surely there are others to mention. --- Another Believer ( Talk ) 22:31, 22 September 2017 (UTC)

David Guido Pietroni
Why was canceled the ten years page with a lot of contributions? Davidasher (talk) 15:59, 30 July 2020 (UTC)

title: Talk:Emergency Contact


text:
Gauthier

Etymology
From a Germanic language (probably ); related to English Walter. For similar development of Germanic w to g in French, see and.

title: Gauthier


text:
Talk:Dawn Sylvia-Stasiewicz

Notability?
I love dogs, and I am a big fan of President Obama. But I can't help but wonder if this article really meets the notability guidelines. It sounds like she was just a dog trainer who happened to train a President's dog. I understand that she had an obituary in the LA times and WaPo, but that is ALL that exists about her in terms of notable sources. Are short obituaries enough on their own to warrant notability? 11 years after creation, this article is 5 (short) sentences. I'm not experienced or savvy enough to feel comfortable marking it as proposed for deletion, but I believe it warrants a discussion. TomFitz77 (talk) 02:27, 6 November 2022 (UTC)

title: Talk:Dawn Sylvia-Stasiewicz


text:
NOT

Noun

 * 1)  A unary operation on logical values that changes true to false, and false to true.

Usage notes

 * The symbols ¬, !, ~, ˈ and Ā have all been used for the NOT operator in various contexts.
 * Boolean variables and states (,, , , etc.) are commonly written in all uppercase in order to distinguish them from the ordinary uses of the words.

Translations

 * French:
 * German: Nicht
 * Japanese: NOT,

Etymology
.

Proper noun

 * : Polish Federation of Engineering Associations

Declension
Indeclinable, or:

title: NOT


text:
ѫзъкъ

Alternative forms

 * Glagolitic:

Etymology
From, from , from. Cognate with 🇨🇬, 🇨🇬.

Adjective

 * 1) tight, narrow

title: ѫзъкъ


text:
Data structures/Introduction

Data Structures ?

Data Structures
Data structures, as is apparent from the name, is a "good" way of holding data. Before attempting to define good, lets see why such a thing is really needed. Every application or program has its set of requirements. Let's take the classic example of a student database at a university. Say, this database needs to hold information like student particulars, staff particulars and course particulars. The data elements student, staff, and course are not trivial elements, they are made of other elements. For instance, the student element is made up of the name element, the age element, and so on. It would make a lot of sense(and a lot of things easy), to hold all the relevant information together. Same is the case with staff element. The structures which help hold such pieces of related information together is called a data structure.

The course element, as one might observe, is more complex. It is made up of the staff(the instructor-in-charge and other instructors), and student(registered student element). The whole thing can be implemented in two ways. One, make a complex element called course, which holds the student and staff elements. This would mean redundancy, as the student and the staff elements already exist, with or without the course element, as they are separate entities. Very obviously, this is a bad solution. Instead, we could have "links" to the already existing student and staff elements. Again, very obviously, this is a more efficient solution (assuming "links" are properly defined). In this case, we have optimized the element or the Data structure for efficiency in terms of space.

Data structures and efficiency
The course element we have designed now seems efficient. But there is an upside to this. Consider a scenario, where the system is presenting a course details to a user. When it needs to present the list of students or staff, it needs to take the link and follow it. Having the elements directly in there would have saved us this overhead. That is, in an attempt to save on space, we are loosing on running time. The reader needs to understand that this loosing time is only relevant in this particular use case of having to display course details.

As is apparent, efficiency of data structures is two fold: Space-wise and Time-wise. The level of compromises one has to make on either depends on the user requirements.

Basic data structures
Linked-List: A linked-list is one of the most basic data structures available. Each element (called a listNode) contains the data being stored, and a pointer to the next, and previous objects in the list (called "next" and "prev" respectively.) Then, we have 2 pointers that point to the first, and last listNodes. In this way, we can find any element in the list, simply by starting either at the beginning or the end, and using the "next" or "prev" pointers to trace through the entire list.

This data structure is very good at inserting elements into the list, since insertion only needs to create the new object, and modify a couple of pointers. However, finding a specific entry in the list takes longer, because following pointers is relatively slow.

Vector: A vector is an array that resizes itself when it doesn't have enough room for its contents. When a vector runs out of space, it will allocate a new chunk of memory that is double the size, and copy all of its current entries over into the new array. This means that the vector's internal structure should have at least 3 things: a pointer to the current array, an integer for the array's size, and another integer for the number of objects being stored. Whenever the number of elements exceeds the size of the array, the array is reallocated, and the old entries are copied over.

This data structure has nearly the same time complexity as an array, since they are driven by basically the same concepts. Adding or removing items from the end is very fast. However, inserting or deleting an item from anywhere else requires all elements above the one being inserted to be shifted, resulting in heavy slowdowns. Searching is fairly quick with vectors. Index lookups are completed in constant time, and searches in a sorted vector can be completed in O(log n). If the vector is unsorted, then it would take O(n) time to find an item. However, a vector is typically quicker than linked-lists for these linear searches, since working in an array is far more efficient for the processor, and results in lots of cache hits.

Note, however that vectors are not suitable for time-critical scenarios, since they face seemingly random slowdowns, when the array has to be reallocated.

Hash Table: A hash table is an array that uses keys for quick look-ups. Using the example at the top of the page, say that we were wanting to store "Student" objects, which contained information on currently enrolled students. In order to use a hash table, we need to select a key. (Preferably a numeric one.) In this example, we would use the Student ID as the key is guaranteed to be different for every student, and it is a number.

This key is put through some sort of calculation so we can link this key to a particular entry inside the array. However, since there are many possible different values for a key, and relatively few spots inside the hash table, there will be collisions when more objects are added to the hash table. There are many different algorithms used in hash tables. Some of them are:

 Separate Chaining : Every entry in the hash table's array is actually a linked-list. We perform look-ups by taking the modulus of the ID and the length of the array, to get an index. Then, if two entries collide, (i.e. they try to use the same index) the second entry is simply added into the linked list. This algorithm is very simple, and good for small databases. However, if many objects are added to the table, lookups will stop being O(1), and will begin looking more like O(log n) searches, or worse.

 Non-Linked List Methods :

These algorithms use vectors with wrap-around, that will resize themselves once they get too full. Most implementations will say a hash table is "too full" when the table is 50% filled.

 Linear Probing : Every entry in the array contains a "status" field, which can either be EMPTY, FULL, or DELETED.
 * When inserting, we take the modulus of the ID and the array length, and if it collides, then we simply increment by 1, until we get to a spot with an EMPTY or a DELETED flag.
 * When looking-up, we take the modulus of the ID and the array length, and if it collides, we increment the index until we either find the value, we get to an EMPTY slot, or until we have traversed the entire array.
 * When deleting, we perform a lookup, and if we find the value, we set the "status" to DELETED.

 Quadratic Probing : This method is very similar to the Linear probing example. The main difference, is that instead of incrementing by 1, we increment by perfect squares. (i.e. 1, 4, 9, ...) This is done, because it can be mathematically proven that if we increment by perfect squares, keep the table under 50% full, and make the table size a prime number, then we will always be able to find an EMPTY or a DELETED spot to insert into. (i.e. We will never enter an infinite loop.)

Note: When doing lookups in quadratic probing, we want to test the original spot, then test the (original spot)+1, then the (original spot)+4, etc.

In all situations, the length of the array is a prime number. If the hash table needs more room, the hash table will find its new size by doubling its current size, and then increasing this number until it is prime. This way, it will avoid situations where various IDs will collide often, because they are multiples of the table-size.

If we need to "re-hash," we resize the old table using the method described in the previous paragraph. We then go item-by-item through the old table, and insert them into the new one.

Generic data structures
The concept of data structure is very requirement-specific. Almost every application which has a good deal of information needs to define its own ways of storing and retrieving data. But, some patterns of requirements have been noted more often than others, and data structures for these have been studied in general. We look at two of them here.

Queues: This is one of the most commonly used data structure. In many cases, one needs a data structure, which hold a set of items, and present the item which had arrived the first. For instance, a lift which queues all the reqest for stops(thought lifts do more complex stuff). This is represented by what is called a Queue data structure.

Dictionary: This is also a very commonly used structure. Imagine having to search for a word in a list of thousands or millions of words. Going through the entire list would be very complex. Given that every two different words have atleast one alphabet difference, we can fairly confidently say that we can come up with a function, which when given the word, can locate a small possible range where the word will exist(i.e. the word is added in that range, using the function). A well devised function can reduce the effort required by hunderds of times. Such a data structure is called a Dictionary, and a very common implementation is called the Hash table.

Tree: It isn't a kind of linear data structure.

--<IP_ADDRESS> 19:44, 28 May 2007 (UTC): Vicky

ja:Topic:データ構造

title: Data structures/Introduction


text:
Radiation Oncology/Breast/Breast chemotherapy

A comprehensive discussion of chemotherapy should be reserved for an Oncology textbook, but general principles of chemotherapy and how it's used with radiation therapy can be discussed here.

Adjuvant Chemo -> RT vs RT -> Chemo

 * Harvard
 * Randomized. 244 pts. Randomized to RT before chemo vs chemo before RT. Chemo was cyclophosphamide, doxorubicin, methotrexate, 5-FU, prednisone (CAMFP) x 12 weeks. 5-year local failure according to margin status - positive margins (14% XRT first, 25% chemo first), close margins <1 mm (0% vs 23%), negative margins (16% vs 0%), unknown margin status (0% vs 20%).
 * 1996 PMID 8614420 — "The sequencing of chemotherapy and radiation therapy after conservative surgery for early-stage breast cancer." Recht A et al. N Engl J Med. 1996 May 23;334(21):1356-61.
 * 2005 PMID 15774786 — "Sequencing of chemotherapy and radiation therapy in early-stage breast cancer: updated results of a prospective randomized trial." Bellon JR et al. J Clin Oncol. 2005 Mar 20;23(9):1934-40. (Presented in abstract form at ASTRO 2001)
 * Median f/u 135 mo. No difference in local or distant failures. Longer time to DM with chemo: 25th percentile reached DF at 56 months (chemo first) vs 37 months (RT first).
 * No difference in any endpoint regardless of sequencing.

Sequential Chemo -> RT vs. Concurrent Chemo-RT

 * Italy (1997-2002)
 * Randomized. 206 patients with quadrantectomy + ALND, pT1-2, SM-. Arm 1) sequential CMF -> RT vs. Arm 2) concurrent CMF + RT. RT given whole breast 50/20 + 10-15 Gy boost
 * 2006 PMID 16226397 -- "A phase III randomized study on the sequencing of radiotherapy and chemotherapy in the conservative management of early-stage breast cancer." (Arcangeli G, Int J Radiat Oncol Biol Phys. 2006 Jan 1;64(1):161-7. Epub 2005 Oct 13.)
 * Outcome: 5-year OS sequential 97% vs concurrent 98% (NS), DFS 86% vs. 87% (NS)
 * Toxicity: acute toxicity mild (NS); late toxicity being evaluated
 * Conclusion: RT can be delayed after completion of chemotherapy (up to 7 months in this study). Concurrent chemo-RT is safe
 * ARCOSEIN trial (France) (1996-2000)
 * Randomized. 716 pts, Stage I-II. Randomized to sequential CT then RT vs concurrent chemo/RT. Chemo was mitoxantrone + 5-FU + cyclophosphamide, 6 cycles q21d. RT 50 Gy/25 fx, optional 10-20 Gy boost.
 * 2007 - PMID 17448869 — "Does concurrent radiochemotherapy affect cosmetic results in the adjuvant setting after breast-conserving surgery? Results of the ARCOSEIN multicenter, Phase III study: patients' and doctors' views." (Toledano A, Int J Radiat Oncol Biol Phys. 2007 May 1;68(1):66-72.)
 * Patient assessment: 92% satisfactory or better. Physician assessment: 60% (concurrent) vs 85% (sequential) satisfactory.
 * Conclusion : Concurrent chemo-RT associated with greater differences between the breasts but no difference in patient satisfaction.
 * Final results, 2007 - PMID 17264336 — "Phase III trial of concurrent or sequential adjuvant chemoradiotherapy after conservative surgery for early-stage breast cancer: final results of the ARCOSEIN trial." Toledano A et al. J Clin Oncol. 2007 Feb 1;25(4):405-10.
 * All patients: no difference in DFS (80%), LRFS (92% vs. 95%), DMFS (87% vs. 84%) or OS (90% vs. 91%)
 * Node positive: 5-year LRFS concurrent 97% vs. sequential 91% (SS)
 * Late toxicity, 2006 PMID 16542788 -- "Concurrent administration of adjuvant chemotherapy and radiotherapy after breast-conserving surgery enhances late toxicities: long-term results of the ARCOSEIN multicenter randomized study." (Toledano A, Int J Radiat Oncol Biol Phys. 2006 Jun 1;65(2):324-32.)
 * Subset of 214 pts assessed by survey. Physical exam and assessment of toxicity using LENT-SOMA scale for breast.
 * Increased fibrosis, telangectasia, hyperpigmentation, and atrophy in concurrent chemo/RT arm. No difference in pain, breast edema, lymphedema.
 * 2004 - PMID 15093200 — "[Radiation and concomitant chemotherapy after surgery for breast cancer]" (French) Calais G et al. Cancer Radiother. 2004 Feb;8(1):39-47.
 * Conclusion : Appealing option for women at high risk of recurrence (node positive). But, increased grade 2 or higher late effects.

Non-randomized studies:
 * Harvard
 * 2006 - PMID 16243442 — "Prospective evaluation of concurrent paclitaxel and radiation therapy after adjuvant doxorubicin and cyclophosphamide chemotherapy for Stage II or III breast cancer." (Burstein HJ, Int J Radiat Oncol Biol Phys. 2006 Feb 1;64(2):496-504.)
 * Prospective, non-randomized. 40 pts. Treated with adjuvant AC x 4, then concurrent taxol (weekly or q3week) + RT. 26 pts intact breast, 14 pts post-mastectomy. Breast dose: 39.6 Gy + boost to 49.6-55.6 Gy. Chest wall: 45 Gy + boost to 49-55 Gy.
 * Dose limiting toxicity in 25%(4 of 16) receiving weekly taxol. In pts receiving q3w taxol, DLT not reached. Grade 2 pneumonitis in 8% (q3w taxol).
 * Concurrent RT with weekly taxol is not feasible after AC chemotherapy.

Adjuvant chemotherapy

 * CMF (cyclophosphamide, methotrexate, 5-FU)
 * Adriamycin-based
 * FEC (5-FU, epirubicin, cyclophosphamide)

Sequential vs alternating

 * NCI Milan - CMF + Adriamycin
 * 403 pts. 4 or more nodes. CMF and Adriamycin q3weeks over 36 weeks. Randomized to sequential chemotherapy (Adriamycin x 4 followed by CMF x 8) vs alternating (2 cycles of CMF alternating with 1 cycle of Adriamycin for 12 total cycles).
 * 10-year results: PMID 7837388 — "Sequential or alternating doxorubicin and CMF regimens in breast cancer with more than three positive nodes. Ten-year results." Bonadonna G et al. JAMA. 1995 Feb 15;273(7):542-7.
 * Improved relapse free survival (42% vs 28%) and overall survival (58% vs 44%) for sequential chemotherapy.
 * Conclusion: benefit for sequential CMF/Adria chemotherapy over alternating chemotherapy. This may be due to giving each chemotherapy drug in a "dose-dense" fashion rather than spreading it out over time.

Sequential vs. concurrent

 * INT-0137 -- concurrent AC vs. sequential dose-intense AC
 * Randomized. 3176 patients s/p surgery, with high-risk N0 or low-risk N+ treated with AC. Randomized to concurrent AC (doxorubicin 54 mg/m2 and cyclophosphamide 1.2 g/m2 Q3W x 6 cycles) vs. sequential AC (doxorubicin 40.5 mg/m2 Q3W x 4 cycles followed by cyclophosphamide 2.4 g/m2 Q2W x 3 cycles). Same dose, but higher intensity in sequential arm
 * 2007 PMID 17308269 -- "Sequenced compared with simultaneous anthracycline and cyclophosphamide in high-risk stage I and II breast cancer: final analysis from INT-0137 (S9313)." (Linden HM, J Clin Oncol. 2007 Feb 20;25(6):656-61.)
 * 5-year outcome: OS 88% vs. 89% (NS)
 * Toxicity: hematologic grade 4 greater with A -> C, nonhematologic comparable
 * Conclusion: Trial does not support dose-intense sequenced therapy

Neoadjuvant chemotherapy

 * General principles: neoadjuvant chemotherapy for breast cancer is chemotherapy given before local therapy (surgery or radiation).
 * Advantages: In comparison to chemotherapy given after surgery (adjuvant chemotherapy), neoadjuvant chemotherapy has certain theoretical advantages:
 * Reduces tumor volume prior to surgery, which may allow for breast conserving surgery rather than mastectomy.
 * Early systemic therapy. Instead of having chemotherapy delayed by several months due to the need for scheduling of surgery and waiting for wound healing, chemotherapy can be given without delay, thus treating micrometastatic disease earlier.
 * Allows in vivo assessment of the chemotherapeutic drug's effectiveness. If the tumor decreases in size after chemotherapy then the oncologist will know the drug is effective.  If the tumor does not decrease in size, then the oncologist can switch to a different drug.
 * Improved tumor vascularity before surgery may allow more of the drug to reach the area around the tumor.
 * Several randomized trials suggested benefit for neoadjuvant chemotherapy, but flaws in design resulted in no difference between arms
 * NSABP B-18 trial demonstrated benefit of neoadjuvant chemotherapy (AC) on higher rates of breast conservation surgery, without impacting DFS or OS. Unfortunately, only 13% patients reached pathological CR
 * NSABP B-27 trial showed the addition of docetaxel to AC did not improve DFS or OS, but improving pCR (10% to 19%) and decreasing local recurrence rate (8% to 5%). Grade 4 toxicity increased (10% to 23%)
 * ''Please see the Post-mastectomy RT section for information about the role of RT after neoadjuvant chemo and mastectomy

 * NSABP B-27 (1995-2000) - Preop AC alone vs Preop ACT vs. Preop AC + postop docetaxel
 * Randomized, 3 arms. 2353 women, only palpable disease allowed (breast or axilla). If primary breast, >1cm (T1c-T3N0-1); any size with axillary adenopathy (T1-3N1). Arm 1) Neoadjuvant AC x4 cycles vs. Arm 2) Neoadjuvant AC x4 then neoadjuvant docetaxel x4 vs. Arm 3) Neoadjuvant AC x4 followed by surgery then adjuvant docetaxel x4. Surgery was lumpectomy + ALDN or mastectomy. All pts received tamoxifen x 5 yrs regardless of ER/PR status. Measurement of tumor (by physical exam) prior to each chemo and before surgery. PMRT not permitted.
 * Preliminary; 2003 PMID 14559892 — "The effect on tumor response of adding sequential preoperative docetaxel to preoperative doxorubicin and cyclophosphamide: preliminary results from National Surgical Adjuvant Breast and Bowel Project Protocol B-27." (Bear HD, J Clin Oncol. 2003 Nov 15;21(22):4165-74. Epub 2003 Oct 14.)
 * Outcome: Higher overall response (CR+PR) for pre-op AC+T group vs AC (90.7% vs 85.5%); higher cCR rate (63% v 40%). No difference in breast conservation rate.
 * Toxicity: Grade 4 AC 10% vs. docetaxel 23%
 * Conclusion: Addition of preop docetaxel significantly increased clinical and pathologic response rates; no impact on BCS
 * 6-years; 2006 - PMID 16606972 — "Sequential Preoperative or Postoperative Docetaxel Added to Preoperative Doxorubicin Plus Cyclophosphamide for Operable Breast Cancer: National Surgical Adjuvant Breast and Bowel Project Protocol B-27" Bear HD et al. J Clin Oncol. 2006 May 1;24(13):2019-27. Median F/U 6.5 years
 * Outcome: pCR AC 9% vs. ACT 19% vs. AC-S-T 10% (SS). LR 8% vs. 5% vs. 5% (SS) Of LR, ~50% were IBTR in women with BCT, other half presumably CW recurrence; regional recurrence all groups 2% (NS); No difference in DFS or OS.
 * Conclusion: Addition of docetaxel no impact on DFS or OS, improved pCR and first LR rate
 * 8-years; 2008 PMID 18258986 -- "Preoperative chemotherapy: updates of National Surgical Adjuvant Breast and Bowel Project Protocols B-18 and B-27." (Rastogi P, J Clin Oncol. 2008 Feb 10;26(5):778-85.) Median F/U 8.5 years
 * Outcome: pCR AC (AC and AC-S-T) 13% vs. ACT 26% (SS); OS 5-year 82-83% (NS), 8-year 74-75% (NS); DFS 5-year 68-71% (NS); 8-year 59-62% (NS). Having pCR significant predictor for DFS and OS
 * Recurrence: IBTR AC 7% vs. ACT 6% vs. AC-S-T 5% (NS); chest wall 4% vs. 2% vs. 3% (NS); regional 3% vs. 2% vs. 3%. Overall taxotere regimens had (SS) fewer first local recurrences
 * Conclusion: Neoadjuvant chemotherapy comparable to adjuvant therapy, and may allow BCS for patients who may not otherwise be candidates

 * NSABP B-18 (1988-1993) - neoadjuvant AC versus postop AC
 * Randomized. 1523 patients. T1-3N0-1 "operable, palpable, non-fixed" (Stage I-IIIA but no cN2 disease). Arm 1) ADJ: Surgery (lumpectomy + ALND or radical mastectomy) followed by 4 cycles doxorubicin and cyclophosphamide (AC) every 21 days, vs. Arm 2) NEO: Same chemotherapy neoadjuvantly, followed by surgery. Surgeons required to state intended surgical procedure at randomization. Tamoxifen x 5 years for age 50+, regardless of ER/PR. In NEO group, pts received breast and lymph node measurement by physical exam before each chemo cycle and before surgery. For lumpectomy group, XRT was given after surgery in the preop group and after chemo in the postop group. No PMRT allowed. cT1 ~30%, cN0 ~75%
 * 1997 PMID 9215816 -- "Effect of preoperative chemotherapy on local-regional disease in women with operable breast cancer: findings from National Surgical Adjuvant Breast and Bowel Project B-18." (Fisher B, J Clin Oncol. 1997 Jul;15(7):2483-93.)
 * Subset analysis. 747 women who received neoadjuvant chemo.
 * Outcome: Breast: cCR 36%. In women with cCR, pCR in 26% (or 9% pCR overall). pCR by cStage: cT1 14%, cT2 9%, cT3 4%. Lymph Nodes: cCR 73%. In women with cCR, pCR in 44% (or 32% pCR overall).
 * Frequency of lumpectomy: NEO proposed 65% vs. performed 67%; ADJ proposed 66% vs. performed 60%. Performed NEO 67% vs. ADJ 60% (SS). Overall 12% more lumpectomies performed. If T3 22% vs. 8% (SS), if T2 71% vs. 63%
 * Conclusion: Preop therapy reduced tumor bulk; 12% more lumpectomies were performed, mostly in tumors >=5 cm. Recommend preop chemo only if lumpectomy not feasible initially or if cosmetic concerns
 * 5-years; 1998 PMID 9704717
 * Outcome: 80% had a decrease in tumor size after chemo. 36% had cCR. 26% with cCR had pCR. Nodal response in 89%: 73% with cCR and 44% pCR. More patients underwent lumpectomy after preop chemo versus postop (67.8% vs 59.8%): increase of 12% in lumpectomies performed. Greatest increase for pts with tumors >5 cm (175% increase). Similar rate of ipsilateral breast recurrence after lumpectomy.
 * 9-years; 2001 PMID 11773300 - "Preoperative chemotherapy in patients with operable breast cancer: nine-year results from National Surgical Adjuvant Breast and Bowel Project B-18." Wolmark N et al. J Natl Cancer Inst Monogr. 2001;(30):96-102.
 * Outcome: OS 5-years 81% vs 80% (NS), 9-years OS 70% vs 69% (NS); DFS 5-years both 67% (NS), 9-year DFS 53-55%). No difference in rates of relapse at different sites. cCR in 36% but only 13% with pCR.
 * Statistically signif. association between clinical response (by physical exam) to neoadj. chemo and survival — 9-year OS 78% for pts with cCR, 67% with cPR, 65% for cNR (defined as stable or progressive dz). DFS was 64%, 54%, 46%. Also, improved OS for those with a pathologic CR versus those with a cCR but residual invasive disease after surgery: 85% vs 73%. Pathologic LN status and primary tumor response are independent factors for OS and DFS.
 * Pathology; 2002 PMID 12209710
 * Conclusion: tumor regression during neoadjuvant treatment may be a surrogate marker for outcome.
 * 16-years; 2008 PMID 18258986 -- "Preoperative chemotherapy: updates of National Surgical Adjuvant Breast and Bowel Project Protocols B-18 and B-27." (Rastogi P, J Clin Oncol. 2008 Feb 10;26(5):778-85.) Median F/U 16 years
 * Outcome: Ability to undergo BCS NEO 68% vs. ADJ 60% (SS); pCR 13%; OS 5-year 81% vs. 80% (NS), 8-year both 72% (NS), 16-year both 55%; DFS 5-year both 67% (NS), 8-year 58% vs. 55 (NS), 16-year 42% vs. 39% (NS). Having pCR significant predictor for DFS and OS
 * By subset: age <50 trend for improved survival with neoadjuvant 16-years 61% vs. 55% (p=0.06); age >50 trend for improved survival with adjuvant 16-year 50% vs. 55% (p=0.07)
 * Recurrence: IBTR (only if lumpectomy) NEO 13% vs. 10% (NS); chest wall both 3% (NS); regional 4% vs. 5% (NS); contralateral 5% vs. 6% (NS)
 * Conclusion: Neoadjuvant chemotherapy comparable to adjuvant therapy, and may allow BCS for patients who may not otherwise be candidates

 * EORTC trial - ??

Prognosis
 * Royal Marsden; 2008 PMID 18592370 -- "The prognostic significance of Ki67 before and after neoadjuvant chemotherapy in breast cancer." (Jones RL, Breast Cancer Res Treat. 2008 Jul 1. [Epub ahead of print])
 * Retrospective. Matched cohort, 103 patients s/p neoadjuvant chemotherapy
 * Predictors for RFS/OS: only Ki-67 significant; not significant age, menstrual status, T stage, N stage, operability, ER, PR, Her2, Grade, histology, LVI, tumor size. 5-year RFS lowest Ki-67 tertile 77% vs. highest tertile 27% (SS); 5-year OS 93% vs. 39% (SS)
 * Conclusion: Post-chemo Ki-67 strong predictor of outcome

Review
 * NCI Symposium; 2008 PMID 18258988 -- "Statement of the science concerning locoregional treatments after preoperative chemotherapy for breast cancer: a National Cancer Institute conference." (Buchholz TA, J Clin Oncol. 2008 Feb 10;26(5):791-7.)
 * Review of evidence for imaging and loco-regional therapy in patients receiving preop chemotherapy
 * Initial workup: initial imaging critical, role for MRI unclear, axillary U/S-guided FNA should be considered
 * Timing of SLND: False negative rate after induction ~10%, comparable to de novo SLND. However, role of SLND in clinically positive patients is unclear
 * BCS: possible more frequently with carefully selected patients
 * RT: Studies evaluating benefit of PMRT after neoadjuvant chemo are small and retrospective

Chemotherapy with hormonal therapy

 * NSABP B-20, 1997 - chemotherapy + tamoxifen vs tamoxifen alone
 * 2306 pts. Randomized to: 1) TAM alone, 2) Methotrexate, 5-FU, tamoxifen (MFT), or 3) CMF + tamoxifen (CMFT).
 * PMID 9390536 — "Tamoxifen and chemotherapy for lymph node-negative, estrogen receptor-positive breast cancer." Fisher B et al. J Natl Cancer Inst. 1997 Nov 19;89(22):1673-82.
 * 5 years f/u. Improved DFS for chemotherapy + tam vs tam alone (90% for MFT, 89% for CMFT, and 85% for TAM; S.S.), improved distant disease free survival (92% v 91% v 87%), overall survival (97% for MFT versus 94% for tamoxifen [P = .05]; 96% for CMFT versus 94% for tamoxifen [P = .03], reduced ipsilateral breast tumor recurrence,
 * Conclusion: chemotherapy still has a benefit even when tamoxifen is used

 * Institut Gustave-Roussy (1989-96)
 * PMID 12196363 Full text, 2002 — "Patterns of failure in a randomized trial of adjuvant chemotherapy in postmenopausal patients with early breast cancer treated with tamoxifen." Arriagada R et al. Ann Oncol. 2002 Sep;13(9):1378-86.
 * Randomized. 835 pts. Included postmenopausal pts who were N+ or grade II-III. Randomized to tamoxifen vs tamoxifen + chemotherapy. Chemo was 6 cycles of FAC or FEC. Pts were treated with lumpectomy or mastectomy.
 * 5-yr DFS 73% (TAM) vs 79% (TAM-CT), p=0.06. 5-yr OS 82% vs 87%, p=0.06. 5-yr DM 22% vs 16% (S.S.). No difference in LC. Chemotherapy more effective in pts who were ER+.
 * Conclusion: chemotherapy is effective in postmenopausal pts receiving tamoxifen.

Taxane-based chemotherapy

 * Intergroup 0148 / CALGB 9344 - PMID 12637460 — "Improved outcomes from adding sequential Paclitaxel but not from escalating Doxorubicin dose in an adjuvant chemotherapy regimen for patients with node-positive primary breast cancer." Henderson IC et al. J Clin Oncol. 2003 Mar 15;21(6):976-83.
 * 3121 pts. Randomized to 4 cycles AC +/- 4 cycles Taxol, each given q3weeks, total of 24 weeks.
 * Addition of Taxol to AC after surgery improves OS in node positive cancers: DFS 70% vs 65%, OS 80% vs 77% at 5-years.

 * NSABP B-28, 2005 (1995-98) - AC x 4 +/- Taxol x 4. node-positive.
 * PMID 15897552 — "Paclitaxel After Doxorubicin Plus Cyclophosphamide As Adjuvant Chemotherapy for Node-Positive Breast Cancer: Results From NSABP B-28." Mamounas EP et al. J Clin Oncol. 2005 Jun 1;23(16):3686-96.
 * 3060 pts. cT1-3 with at least 1 positive node, treated with lumpectomy + node-dissection or mastectomy. Breast XRT (no axillary RT) after last cycle of chemo. No post-mastectomy RT. Tamoxifen allowed.
 * 64 month median f/u. 5-year DFS 76% (AC/T) vs 72% (AC), S.S. No difference in 5-year OS, 85% in both arms.

Docetaxel:
 * Breast Cancer International Research Group BCIRG 001, 2005 (1997-99) - PMID 15930421 — "Adjuvant docetaxel for node-positive breast cancer." (Martin M et al, N Engl J Med 352(22):2302-13,2005)
 * 1480 pts. Node-positive, not fixed or matted (no cN2), T1-3. Randomized after surgery to TAC (taxotere, adriamycin, cyclophosphamide) vs FAC x 6 cycles q3weeks.
 * Median f/u 55 m. 5-year DFS 75% (TAC) vs 68% (FAC). 28% reduction in relapse. 30% lower risk of death. OS 87% vs 81%.

Dose-dense chemotherapy

 * Intergroup / CALGB 9741, 2003
 * 2005 pts. Node positive. Every 2 weeks AC/T vs standard dose q3weeks. 2x2 factorial design. Randomized to: Sequential A x 4 -> T x 4 -> C x 4 q3week / 36 wks, Sequential A->T->C q2week / 24 wks, Concurrent AC x 4 -> T x 4 q3w / 24 wks, or Concurrent AC x 4 -> T x 4 q2week / 16 wks. Filgrastim (G-CSF) given with dose-dense chemo.
 * First report: PMID 12668651
 * 7% improvement in DFS (82% vs 75%) for dose-dense (RR=0.74), 2% OS at 3 years (RR=.69). No difference between concurrent and sequential arms. Less neutropenia, less need for hospitalization, and lower incidence of other toxicities with the dose-dense approach.

Stem-Cell Transplant

 * SWOG 9623
 * 2007 PMID 17404368 -- "Intensive dose-dense compared with high-dose adjuvant chemotherapy for high-risk operable breast cancer: Southwest Oncology Group/Intergroup study 9623." (Moore HC, J Clin Oncol. 2007 May 1;25(13):1677-82.)
 * Randomized. 536 patients, BCA s/p lumpectomy/mastectomy, with >=4 LN+. Treated with 1) AC-HD vs. 2) ATC
 * 5-year outcome: No difference in OS (88% vs. 84%) or DFS (80% vs. 75%)
 * Conclusion: transplantation not superior to dose-dense dose-escalated therapy, higher toxicity

Meta-analysis

 * Early Breast Cancer Trialists' Collaborative Group (a.k.a. Oxford overview) - Meta-analysis of chemotherapy
 * See also: Oxford overview of Radiotherapy or Hormonal therapy
 * Early results, 1988 - PMID 3205265 — "Effects of adjuvant tamoxifen and of cytotoxic therapy on mortality in early breast cancer. An overview of 61 randomized trials among 28,896 women." N Engl J Med. 1988 Dec 29;319(26):1681-92.
 * 61 trials. 28,896 women.
 * 1992 - PMID 1345869 — "Systemic treatment of early breast cancer by hormonal, cytotoxic, or immune therapy. 133 randomised trials involving 31,000 recurrences and 24,000 deaths among 75,000 women."
 * 131 trials. 75,000 women.
 * 1998 - PMID 9752815 — "Polychemotherapy for early breast cancer: an overview of the randomised trials." Lancet. 1998 Sep 19;352(9132):930-42.
 * Prolonged polychemotherapy vs no chemo (47 trials, 18,000 women); long vs short polychemo (11; 6,000); anthracycline-based vs CMF (11; 6,000).
 * Polychemo: reduced recurrences by 35% (age < 50), 20% (age 50-69); mortality 27% (<50), 11% (50-69). Recurrence reductions in first 5 years.  Survival benefit grew during first 10 yrs. Results in 10-year OS difference for node-negative pts 71% vs 78% (absolute 7% gain) or 42% vs 53% (11% benefit) for node-positive. Smaller benefit for age > 50.
 * No advantage for more than 3-6 months of chemo. Anthracycline-based better than CMF for recurrence and survival (69% vs 72% 5-yr OS
 * 2005 - PMID 15894097 — "Effects of chemotherapy and hormonal therapy for early breast cancer on recurrence and 15-year survival: an overview of the randomised trials." Early Breast Cancer Trialists' Collaborative Group (EBCTCG). Lancet. 2005 May 14-20;365(9472):1687-717.

 * Her2 and Anthracyclines
 * 2008 PMID 18159072 -- "HER2 status and efficacy of adjuvant anthracyclines in early breast cancer: a pooled analysis of randomized trials." (Gennari A, J Natl Cancer Inst. 2008 Jan 2;100(1):14-20. Epub 2007 Dec 25.)
 * Pooled analysis, 8 trials, 6564 patients, 5354 with her2 info available, 29% her2+.
 * Her2+ patients: anthracycline-based chemo superior to non-anthracyclines in DFS (HR 0.71, SS) and OS (HR 0.73, SS)
 * Her2- patients: no impact of anthracyclines on DFS (HR 1.00, NS) or OS (HR 1.03, NS)
 * Conclusion: Added benefit of adjuvant anthracyclines appears confined to women with her2 overexpression

Herceptin (trastuzumab)
Known to improve time to progression in metastatic disease in pts with her-2-neu overexpressing tumors when combined with standard chemotherapy.

Adjuvant setting:
 * M.D.Anderson, 2005 (2001-3) - Herceptin plus Taxol/FEC chemotherapy. Evaluate pCR.
 * PMID 15738535 — "Significantly higher pathologic complete remission rate after neoadjuvant therapy with trastuzumab, Paclitaxel, and epirubicin chemotherapy: results of a randomized trial in human epidermal growth factor receptor 2-positive operable breast cancer." Buzdar AU et al. J Clin Oncol. 2005 Jun 1;23(16):3676-85.
 * 42 pts. Stage II-IIIA, Her-2-neu 3+ or positive by FISH. Taxol x 4, then FEC x 4 then surgery + RT. Randomized to +/- weekly Herceptin x 24 weeks concurrent with first chemotherapy cycle.
 * pCR in 26% (chemo) vs 65.2% (Herceptin). Trial stopped early

 * NSABP B-31 and NCCTG N9831, 2005
 * NSABP B-31 (2000-05)
 * Operable breast cancer, Her-2 positive with LN+. Required FISH amplification or 3+ by immunohistochemistry. Required axillary dissection.
 * Two arms: 1) ACx4 -> Taxol x 4, 2) Same chemo + Herceptin weekly x 1 yr (beginning with first Taxol dose). Taxol was q3w (in 90%). Herceptin 2 mg/kg.
 * NCCTG N9831 (2000-05)
 * Also enrolled high-risk node-negative disease (as of 2003) - >2 cm and ER+ or PR+, or >1 cm and ER-/PR-. Allowed sentinal lymph node.
 * Three arms: 1) ACx4 -> weekly Taxol x 12, 2) ACx4 -> weekly Taxol x 12 -> Herceptin 1 yr, 3) ACx4 -> Taxol + Herceptin (started together)
 * The two trials had some minor differences in the sequencing of Taxol, hormonal therapy, and RT, but were quite similar.
 * Combined results:
 * Interim; 2005 PMID 16236738 Full text — "Trastuzumab plus adjuvant chemotherapy for operable HER2-positive breast cancer." Romond EH et al. N Engl J Med. 2005 Oct 20;353(16):1673-84.
 * Interim analysis of 2043 pts (of planned 2700) in B-31 and 1633 (of 2000) in NCCTG.
 * 3-yr DFS improved by 12% in Herceptin arms. Risk of death decreased by 33%. Up to 4.1% incidence of NYHA Class III-IV heart failure. 8% decrease in DM. Isolated brain metastases more common in herceptin group. Sequential administration of H may be inferior to concurrent administration with chemo.
 * 4-years; 2011 PMID 21768458 -- "Four-Year Follow-Up of Trastuzumab Plus Adjuvant Chemotherapy for Operable Human Epidermal Growth Factor Receptor 2-Positive Breast Cancer: Joint Analysis of Data From NCCTG N9831 and NSABP B-31." (Perez EA, J Clin Oncol. 2011 Jul 18. [Epub ahead of print])
 * Significant reduction in DFS and 39% reduction in deaths.
 * Cardiac dysfunction; 2005 PMID 16258083 — "Assessment of cardiac dysfunction in a randomized trial comparing doxorubicin and cyclophosphamide followed by paclitaxel, with or without trastuzumab as adjuvant therapy in node-positive, human epidermal growth factor receptor 2-overexpressing breast cancer: NSABP B-31." Tan-Chiu E et al. J Clin Oncol. 2005 Nov 1;23(31):7811-9.
 * Concurrent H+RT; 2009 PMID 19349549 -- "Radiotherapy and adjuvant trastuzumab in operable breast cancer: tolerability and adverse event data from the NCCTG Phase III Trial N9831." (Halyard MY, J Clin Oncol. 2009 Jun 1;27(16):2638-44. Epub 2009 Apr 6.)
 * Subset analysis of 1503 patients. No RT to IM nodes. Median F/U 3.7 years
 * Outcome: No difference for acute skin reaction, pneumonitis, dyspnea, cough, dysphagia, or neutropenia. Worse leukopenia for AC-TH vs AC-T (OR 1.9). No difference of cardiac events, regardless of side (cumulative incidence ~2.5%)
 * Conclusion: Concurrent adjuvant RT and herceptin not associated with increased acute adverse effects

 * Herceptin Adjuvant (HERA), 2005 (2001-05) - also called BIG (Breast International Group) 01-01
 * 5081 pts. LN+ or LN- and >1 cm. Pts randomized after completing adjuvant therapy. Had to have a minimum of 4 cycles.
 * Randomized to 1) observation, 2) 1 year, or 3) 2 years of Herceptin. Herceptin given q3w (at 6 mg/kg).
 * Results:
 * PMID 16236737, 2005 Full text — "Trastuzumab after adjuvant chemotherapy in HER2-positive breast cancer." Piccart-Gebhart MJ et al. N Engl J Med. 2005 Oct 20;353(16):1659-72.
 * Interim analysis performed for the one year treatment group. 2-yr DFS improved 8.4%, 50% reduction. No difference in OS. 33% developed brain mets.
 * 2-yr update: PMID 17208639, 2007 — "2-year follow-up of trastuzumab after adjuvant chemotherapy in HER2-positive breast cancer: a randomised controlled trial." Smith I et al. Lancet. 2007 Jan 6;369(9555):29-36.
 * After a median follow-up of 2 years there is a significant overall survival benefit for adjuvant trastuzumab. The unadjusted hazard ratio (HR) for the risk of death with trastuzumab compared with observation alone was 0.66 (95% CI 0.47-0.91; p=0.0115).

 * FinHer, 2006 (2000-2003)
 * 232 women, LN+ or high risk LN- (tumor > 2 cm and ER/PR-), with amplified HER2/neu gene. Randomized to 9 weekly trastuzumab cycles vs no trastuzumab concurrent with chemotherapy (docetaxel or vinorelbine x 3 cycles q3w (weeks 1,4,7) +/- trastuzumab, followed by FEC (flurouracil, epirubicin, and cyclophosphamide) x 3 cycles q3w).
 * Note: The her2neu+ randomization was a subset of a larger trial of 1010 women total, randomized to docetaxel vs vinorelbine followed by FEC, as above.
 * Results:
 * PMID 16495393, 2006 — "Adjuvant docetaxel or vinorelbine with or without trastuzumab for breast cancer." Joensuu H et al. N Engl J Med. 2006 Feb 23;354(8):809-20.
 * 3-year recurrence-free survival better in those who received trastuzumab (89 percent vs. 78 percent; P=0.01). Trastuzumab was not associated with decreased left ventricular ejection fraction or cardiac failure.

CDK4/6 Inhibitors

 * Approved CDK4/6 Inhibitors:
 * Palbociclib (Ibrance): Approved for the treatment of HR+/HER2- advanced or metastatic breast cancer in combination with hormone therapy.
 * Ribociclib (Kisqali): Approved for HR+/HER2- advanced or metastatic breast cancer in combination with hormone therapy.
 * Abemaciclib (Verzenio): Approved for HR+/HER2- advanced or metastatic breast cancer as monotherapy or in combination with hormone therapy.
 * Tim Dukelow et al. CDK4/6 inhibitors in breast cancer. Anticancer Drugs. 2015 Sep;26(8):797-806. ( 26053278)
 * Laura M Spring et al. CDK 4/6 Inhibitors in Breast Cancer: Current Controversies and Future Directions. Curr Oncol Rep. 2019 Feb 26;21(3):25. ( 30806829)

Multigene assays for risk assessment

 * Oncogene DX
 * Oncotype studies
 * PMID 15591335, 2004 — "A multigene assay to predict recurrence of tamoxifen-treated, node-negative breast cancer." Paik S et al. N Engl J Med. 2004 Dec 30;351(27):2817-26.
 * Likelihood of distant recurrence in women with node-negative, ER-positive tumors. Studied 21 prospectively-identified genes. Cohort of 668 pts from NSABP B-14.
 * Conclusion: Positive validation study. Oncotype DX assay accurately predicts risk of DM.

Erythropoietin

 * Breast Cancer Erythropoietin Survival Trial (BEST) (Multi-national: Canada, Europe, Australia, South Africa)(2000-2002)
 * Randomized. Stopped early due to adverse outcomes. 939 patients, metastatic breast CA. Arm 1) placebo vs. Arm 2) Epo to maintain Hgb 12-14 g/dL, and initiated if Hgb <13 g/dL
 * 2005 PMID 16087945 -- "Maintaining normal hemoglobin levels with epoetin alfa in mainly nonanemic patients with metastatic breast cancer receiving first-line chemotherapy: a survival study." (Leyland-Jones B, J Clin Oncol. 2005 Sep 1;23(25):5960-72. Epub 2005 Aug 8.)
 * Outcome: 1-year OS placebo 76% vs. Epo 70% (SS); no difference in tumor response
 * Conclusion: Epo use to maintain high Hgb was associated with decreased survival


text:
Neorufalda

Neorufalda, is a monotypic snout moth genus described by Hiroshi Yamanaka in 1986. Its single species, Neorufalda pullella, described in the same article, is found in Japan.

title: Neorufalda


text:
Wikipedia:WikiProject Spam/LinkReports/kolabnow.com

Links

 * kolabnow.com resolves to [//<IP_ADDRESS> <IP_ADDRESS>]
 * Link is not on the blacklist.
 * Link is not on the domainredlist.
 * Link is not on the Monitorlist.
 * None of the mentioned users is on the blacklist.
 * Link is not on the whitelist.
 * Link is not on the monitor list.
 * Link is not on the whitelist.
 * Link is not on the monitor list.

Additions

 * Displayed all 1 additions.


text:
Zara Alvarez

Zara Alvarez (25 March 1981 – 17 August 2020) was a Filipina human rights advocate, educator, paralegal, and prominent social activist who predominantly campaigned against human rights violations during the administration of Rodrigo Duterte. She was well known for her active campaign to protect human rights in the Philippines, which became a matter of concern during the presidency of Rodrigo Duterte. During her career as a human rights activist, she was often a prime target of political mafia and reported to have received numerous death threats due to her active campaigns against human rights violations. On 17 August 2020, she was assassinated by unknown gunmen. According to human rights groups, her murder suggested a serious major crackdown against human rights activists and civilians in the Philippines.

Career
Alvarez, a single mother, was actively involved in social activism and served as a paralegal staffer helping to spotlight cases regarding human rights violations on Negros Island to the United Nations Human Rights Council. She also worked as a volunteer for the human rights organisation Karapatan where she served as the education director and also associated closely with the Negros Island Health Integrated Program as an advocacy officer.

In 2018, she was purposely included in an official terror list among 600 individuals by the Duterte administration to silence her. She was detained by the Philippine National Police for nearly two years until 2020.

In a manifestation filed with the Supreme Court of the Philippines on 1 September 2020, Karapatan said Alvarez was supposed to be a witness on the red-tagging and harassment of human rights workers.

Murder
On 17 August 2020, at around 8 pm, she was reportedly shot several times by unidentified gunmen along the Sta. Maria Street in Eroreco, Barangay Mandalagan, Bacolod. She was apparently targeted by gunmen while she was heading home after buying dinner.

She was killed on the day of the funeral of peace activist Randall Echanis, who was assassinated on 10 August 2020. She was the 13th member of Karapatan to be murdered since Rodrigo Duterte came to power in 2016.

Reactions
International rights group International Coalition for Human Rights condemned and denounced the killing of the activist and, in an official statement, it stated that Alvarez was a brave figure and staunch defender of farmers and Filipino rights.

Her murder sparked hot debate in the international community criticizing the newly passed Anti-Terrorism Act of 2020 (Republic Act No. 11479), a measure giving the government more powers to act against persons or groups falling under what critics say is a dangerous and vague definition of terrorism.

In light of Alvarez's murder, the House of Representatives requested the Supreme Court to make it easier for rights activists such as Alvarez to seek protection under the writ of amparo. The Supreme Court administrator said the court will review guidelines for the writ.

title: Zara Alvarez


text:
Brighton tornado

The Brighton tornado is the strongest storm recorded in Melbourne to date.

On the afternoon of 2 February 1918, with prevailing north-westerly winds and a heat wave (typical conditions for Melbourne thunderstorms). After a severe storm formed and moved off Port Phillip, two tornadoes struck Brighton beach simultaneously at approximately 5:45 pm and proceeded inland, converging near the junction of Halifax and Church Streets. Five minutes later, a third tornado struck. The tornadoes then tracked east over open fields.

Damage retrospectively rated F3 on the Fujita scale was observed in places. Two people were killed, a man and a boy, while the drowning of a woman at St Kilda beach is believed to be related to the same storm cell. Over 6 were injured in the Brighton area.

The tornado completely destroyed the Hawthorn Road Methodist church, which was later rebuilt. Numerous homes were demolished. The tornado badly damaged the Brighton Baths, tore the roof off Royal Terminus Hotel and destroyed the verandah of Grimley's Hotel. Extensive damage was incurred to infrastructure on the Sandringham railway line. Several community and sporting facilities were destroyed including the cricket club grandstand and a bandstand. It also damaged the burial monument of Adam Lindsay Gordon in the Brighton general cemetery.

title: Brighton tornado


text:
User:Dayanjan/Books/Metabolomics and Inflammation

Investigation of global metabolic changes associated with inflammation

 * Inflammation
 * Analytical chemistry


text:
Talk:Operating System Design/Contents

suggestion
The book contents should be improved in many aspects. I am going to discuss some of them in order to improve the book. Here is the overall material commonly covered in an OS textbook.
 * Introduction and History
 * Process
 * Process Concept
 * Process States
 * Inter Process Communication
 * Process Scheduling
 * Synchronization
 * Deadlock
 * Thread (Light Weight Process)
 * Memory Management
 * Basic Models
 * Virtual Memory
 * Segmentation
 * Paging
 * Filesystem
 * File Abstraction
 * Issues
 * Performance
 * Fault-tolerance
 * Security and Protection

WARNING
Unless somebody objects I am going to hijack this book project and start over. I can't write a complete book on this subject but I can do about 75% and I can provide what I hope is a rational overall structure.

I am much more interested in the history of and rationale for operating systems than I am in the details of the popular contemporary systems. Myself I use Linux these days, but my experience goes back to the ten card loader for the IBM 704.

old stuff
You will find that for a book to be successful it is better to allow people to contribute and colloborate directly - You might find the controversial ASQ page has much of interest for you. Anyway good luck Lobster 12:54, 16 Oct 2004 (UTC)

Thanks, Lobster. I'll change it now. If people want to contribute it would be prefered that they discuss it here first though. Wranga

change title
There are some who feel that a title such as 'my perfect OS' - could not be the title of a text book - (that it is just opinion) so I would suggest giving it some serious title such as "Perfecting Operating System Design" - it sounds silly but these people are control freaks and prefer everyone to conform to their vision limitations - I warn you now :-) Also turn your editing to minor edits as you are still developing the book - good luck :-) Lobster 07:38, 17 Oct 2004 (UTC)

operating system wiki
The TUNES project also involves creating an improved operating system. They have a wiki now:
 * TUNES wiki http://cliki.tunes.org/index

So, does "My Perfect OS" have any new idea that haven't already been discussed to death over on the TUNES wiki ?

Also check out the ideas at
 * Killer Operating System http://c2.com/cgi/wiki?KillerOperatingSystem

ReactOS
ReactOS is almost similar to "My Perfect OS" -- Bijee

Linux Considerations
Requirements to be modular, open, and easy to use are already being rapidly satisfied in many Linux distributions.

Here are a couple of friendly desktops:

 * Ubuntu Linux
 * Morphix - Very modular!

Because Linux is already so advanced, much of the work is already done. Additionally, many linux distributions are accompanied by LiveDistros which give you a full operating system that boots from a cd, dvd, usb stick, or other bootable media devices. These bootable LiveDistros are useful because there are already tools out there to remaster these, giving you your own, unique operating system customized to include your own desktop background, browser bookmarks, applications and more.

Software Analogs
Here's a list of software that is free and can easily be added to My Perfect OS

 * http://www.demosoftware.net/docs/gfdl/equivalents_english_table.html

This is pointless...
This book is pointless, quotes like

"The OS should almost definitely be built upon FreeDOS (http://www.freedos.org/) (or on its 32 bit counterpart, FreeDOS-32 (http://freedos-32.sourceforge.net/)) like Windows 9x is upon MS-DOS. This would enable users to access and maintain and repair their computers when the GUI isn't working."

and

"Linux is best as a server, but average PC users are not familiar with its concepts and simplicity, hence will never be much of a competition to MS Windows."

clearly show that this has been written by a bunch of people too lazy to learn some simple linux command line tools.

go rtfm rather than making up bullshit.

---

While the above user is a wee bit harsh... I see a little truth in it. I don't exactly see where this book is going, nor how I can make this book better. --Dragontamer

ReactOS
You may as well just make a reactos distro reactos.com (they've been having some server problems recently) if your going to clone directx api at least help them do it. they're working on cloning windows itself. (which would make something that's just similary programmed obsolete.)

Where Are MacOS
Where is MacOS i think it was missing!

Embedded Systems
In the Embedded Systems book, We talk alot about Real-Time OS's, and i think that perhaps we could post links between these two books. -- 22:16, 28 November 2005 (UTC)

"< Operating System Design" links point to cover page rather than contents page.
The "< Operating System Design" links point to the cover page rather than the contents page, meaning that people have to click through to the contents page again every time they exit a chapter. Irrevenant 09:05, 24 April 2006 (UTC)

Rearrange Titles
I think this book should have the TOC rearranged some. It's very messy, and does not go in the actual order of development. You SHOULD NOT be working on getting a process into memory UNTIL you have memory management of some type.

Threads versus Processes
A Thread is basically a subset of a Process. Some of the management is removed but generally the same issues exist. Wouldn't the discussion of Threads be better off as a subset of Processes.

The list at the top of this page is a decent start, but omits Initialisation. The order of topics being covered can vary depending on whether you want to go through order of development, or order of running, but the basics that should be covered are:
 * Initialisation
 * Boot Loaders (including multi stage ones)
 * Hardware Initialisation (after the OS has loaded)
 * Tasks (Processes if you prefer)
 * Definition
 * Scheduling
 * First Come First Served
 * Run Shortest First
 * Run First to Complete
 * Time slicing
 * Pre-emption
 * Prioritising
 * Concurrent processing
 * Deadlock
 * Livelock
 * Interprocess Communication
 * Semaphores
 * Shared Memory
 * Threads (Lightweight processes)
 * Memory Management
 * Basics
 * Allocation Algorithms
 * Segmentation
 * Virtual Memory
 * Paging
 * Swapping
 * Fault Tolerance (Page Deallocation tables)
 * File Systems
 * Abstractions
 * Allocation Algorithms
 * Performance
 * Fault Tolerance
 * RAID
 * Moving Bad Blocks
 * Journalling
 * Security
 * Access Controls
 * Users
 * Resources
 * Privileges

Continuing Work
I see that some edits have been done... I've tried to tidy some of the pages up a bit, and mostly I'm working from memory here so if I make mistakes please correct me. It seems like some of the pieces that have been added are very minor, but still if we can get some more pages in place perhaps we can make this actually useful...

I've not added any specific implementation chunks in as I'm not sure what the best way to do it would be... Explicit copies of portions of Open OSes that match the descriptions, or custom pseudocode that at least helps the would be learner to understand what they would need to write? Any thoughts any one? --Zwack 17:51, 28 October 2007 (UTC)

title: Talk:Operating System Design/Contents


text:
Wikiversity:Culture

Wikiversity's culture of diplomatic honesty and good faith is important.

"..... the idea here is to also host learning communities, so people who are actually trying to learn, actually have a place to come and interact and help each other figure out how to learn things." (Jimbo Wales - In the opening session of Wikimania 2006 talking about Wikiversity)

This section explores Wikiversity's image, mission and effectiveness in terms of its social aspects.

Structure
The use of namespaces at Wikiversity is perhaps one of its the most unique and innovative features, particularly the addition of School: and Topic:, which designate what might traditionally be thought of as "departments" or "divisions" within a "brick and mortar" university. But as we develop Wikiversity, we should pay more attention to the User: namespace than is allowed by the policies on other Wikimedia projects for a variety of reasons. As our policies form, we must realize that personal expression, interpersonal dialog and cultural distinction are inherent parts of a typical university environment, both in brick-and-mortar institutions and online learning networks.

People
Wikiversity participants (occasionally called Wikiversitans) are generally creative, thoughtful people who come here to do serious work, growing as learners and teachers, producing useful work and making a positive difference in their World. But we also have less serious sides, playful sides. As members of a tightly-knit learning community, we learn to express ourselves responsibly and allow ourselves to be impressed upon by others, thereby forming interpersonal relationship through our encounters. We join groups of like-minded folks through Schools, Topics, and other group learning situations where we focus on the tasks at hand. In the process, we learn to work together to achieve learning goals, which can be both individual and collective.

When we build our userpages, we are acutely aware of how public they are. Everyone has a different personality. Some people may not create a userpage because they are shy or it is not important to them. (See Special:Logs for evidence.) Others go to extremes to make an impression. Everytime we edit a page, we risk "face" because of MediaWiki's ability to track our every move. Doing something "foolish", as most wiki users know, seldom goes "unpunished". However, as long as users make edits in good faith, it is not hard to save face. Learning what is appropriate and where, is not a bad priority for the responsible Wikiversitan. It is important to develop centers of culture at Wikiversity that allow the freedom of expression.

It is also important to realize that we have a "collective face" to those outside our circle.

Relationships
As a Campus, our "places" and "spaces" matter. All users are allowed their own personal space in the form of user subpages for self-reflection and the development of organized thoughts that we are working through individually. There are as many ways to use these subpages as there are Wikiversity users. As we assume good faith, we learn to respect each other's privacy through the practice of good netizenship. We learn to understand each other's identity, tolerate each other's idiosyncrasies, and develop ways to foster mutual respect. We also learn to balance scholarship, focus, and fun, while getting better at what we do as topic-focused teams, taskforces, interest groups and scholarly associations, large and small. Through association with others within our online shared spaces, practice is the only way to learn netizenship. Schools, Divisions and Departments are collections of both people and learning resources. Our culture and Wikiversity's relaxed policies allow us to develop as individuals within a comfort zone unique in the context of the larger Wikimedia metacommunity. One cannot fully think about developing Wikiversity without being aware of its culture.

As our learning community grows, our hope is to produce not only valuable learning resources, but also better people who indeed can bring about positive social change both online and in the real world.

title: Wikiversity:Culture


text:
Talk:Rampage (mascot)

A Commons file used on this page has been nominated for deletion
The following Wikimedia Commons file used on this page has been nominated for deletion: Participate in the deletion discussion at the. —Community Tech bot (talk) 09:06, 21 March 2019 (UTC)
 * PHI6.jpg

title: Talk:Rampage (mascot)


text:
Krzysztof Chrobak

Krzysztof Chrobak (born 3 October 1957) is a Polish football manager who is currently in charge of Widzew Łódź II.

title: Krzysztof Chrobak


text:
Rich and Famous

Rich and Famous may refer to:

Theatre and film

 * Rich and Famous (play), a 1974 John Guare play
 * Rich and Famous (1981 film), starring Jacqueline Bisset and Candice Bergen
 * Rich and Famous (1987 film), Hong Kong film directed by Taylor Wong
 * Rich and Famous a show from the ITV Studios

Music

 * Rich and Famous (Buddy Rich album), a 1983 album by the Buddy Rich Big Band
 * Rich and Famous (Blue Mercedes album), a 1988 album by Blue Mercedes.
 * Rich and Famous (Vice Squad album), by U.K band Vice Squad produced by Paul Rooney
 * Rich & Famous, an EP by Accept
 * "Rich and Famous", a song written by Kai Hansen and performed by German power metal band Gamma Ray

title: Rich and Famous


text:
Larry Woodall

Charles Lawrence "Larry" Woodall (July 26, 1894 – May 6, 1963) was an American professional baseball player and coach. He played ten seasons in Major League Baseball, all in the American League with the Detroit Tigers (1920–1929), primarily as a catcher.

Life
Born in Staunton, Virginia, he attended Wake Forest University and the University of North Carolina.

Career
During most of Woodall's playing career, he played behind two starting catchers of the Tigers, Johnny Bassler and Oscar Stanage. For one season in 1927, however, he played a career-high 86 games at catcher during manager George Moriarty's first season. Woodall posted a .997 fielding percentage (committing one error), the best percentage among all starting catchers that season. He hit over .300 in three seasons and had a career batting average of .268 in 548 games. Woodall batted and threw right-handed.

After his major league career was over, Woodall spent ten seasons in the Pacific Coast League. In 1930–31, he played for the Portland Beavers, including a stint as player-manager in 1930. He moved on to the Sacramento Senators in 1932–33, then put in six seasons with the San Francisco Seals from 1934 to 1939.

Woodall's post-playing career included more than two decades with the Boston Red Sox, as a coach (1942–1948, including service on Boston's 1946 pennant-winning team), director of public relations, and scout. In 1949, he scouted Willie Mays but reported that Mays "was not the Red Sox' type of player." Woodall remained a Red Sox employee until his death at age 68 in Cambridge, Massachusetts.

title: Larry Woodall


text:
Björn-Erik Höijer

Björn-Erik Höijer (14 March 1907 – 10 February 1996) was a Swedish novelist, short-story writer and playwright.

Biography
Björn-Erik Höijer was born at Malmberget, Sweden. Originally a handicraft teacher (sloyd), Höijer made his literary debut in 1940 with the short-story collection Grått berg. Among his novels are Parentation from 1945 and Lavinen from 1961. Among his plays are Isak Juntti hade många söner from 1954 and En gruvarbetares död from 1990. He was awarded the Dobloug Prize in 1967. He died during 1996 and was buried at Uppsala gamla kyrkogård.

title: Björn-Erik Höijer


text:
PHP/Dates

PHP Dates and Times
One of the most challenging subjects for beginning coders to deal with in learning PHP can be accurately dealing with dates and times. Thankfully, this scripting language is equipped with a very complete set of functions to deal with date and time manipulation. This article will cover some of the basic functions and usage that PHP contains.

Date

 * The most basic, and quite possibly the most useful function at your disposal for manipulating dates is appropriately named "date." This function accepts one or two parameters. The first is a string value that represents the format in which you wish your date and/or time to be displayed. The variety of options available to be used can be found in the PHP manual. The second parameter is an optional UNIX timestamp that tells PHP what date and time you want to be displayed. If the second parameter is left empty, the date function will default to the current UNIX timestamp.

 * Example:

Time

 * The time function takes no parameters and simply returns the current UNIX timestamp. Without going into undue detail, remember that the UNIX timestamp is the number of seconds that have elapsed since the UNIX Epoch (Jan 1, 1970 00:00:00 GMT). With this definition, we can easily see how to select times and dates exact increments from our present time.

 * Example:

Mktime

 * While the time function allows us to calculate quite easily based on the current UNIX timestamp, mktime allows us to specify an exact moment in time (with some limitations ). The function accepts 0-7 optional parameters. Leaving all parameters off of the function call causes the same value to be returned as that of the time function. However, the breakdown and flexibility of this function can be clearly seen as we look at the parameters.

 * 1) Hour – 0 through 24
 * 2) Minute – 0 through 60
 * 3) Second – 0 through 60
 * 4) Month – 0 through 12
 * 5) Day – 1 through the number of days in the month selected
 * 6) Year – 1970 through 2038 (view limitations)
 * 7) DST (Daylight Savings Time) – 0 for no, 1 for yes, or -1 for unsure

 * The ranges of values I present here are not actually limitations, but rather references for you to see how the function is intended to work. You may present any valid integer to any of the parameters, and mktime will attempt to calculate the proper UNIX timestamp.

 * Example:

 * Notice in the second example that I reference the month of January 1994 by calling the 13th month of 1993 instead. Mktime allows for such calculations, and because of this, we can come up with some very dynamic date and time calculations.

Strtotime

 * Strtotime is a slightly different animal than mktime, but it serves the same overarching purpose: it allows us to reference a specific date and/or time and gives us the UNIX timestamp for that time. The difference between the functions, though, is substantial. Strtotime accepts nearly any human readable string as its first, required parameter. So, one could actually pass in something like January 1 or next Thursday to the function, and the appropriate timestamp is calculated. There is also a second, optional parameter that allows you to pass in the timestamp from which to calculate.

 * Example:

Putting it All Together
After the basic functions we have reviewed, I'm sure you can see some incredible possibilities in date and time manipulation. If you are still struggling with joining these most basic of the date/time functions together, consider this final example in which we create a tabular calendar of the current month. \n"; ?>

There are so many other date and time functions in addition to these at your disposal, and I just don't have the time to cover them all. Study and choose what combination of functions works best for your situation, and you will be amazed at how powerful these functions can be.

Good luck!

title: PHP/Dates


text:
1997–98 Bosnia and Herzegovina Football Cup

1997–98 Bosnia and Herzegovina Football Cup was the fourth season of the Bosnia and Herzegovina's annual football cup. The Cup was won by Sarajevo who defeated Orašje in the super final.

Overview
An agreement was signed between the Football Federation of Bosnia and Herzegovina and the Football Federation of Herzeg-Bosnia to make the final between the winners of the respective cups.

Round of 16
The matches were played on 28 February and 1 March 1998.

 * }

Quarterfinals
The first legs were played on 11 March and the second legs were played on 25 March 1998.

 * }

Semifinals
The first legs were played on 8 April and the second legs were played on 22 April 1998.

 * }

Super final

 * }


text:
User:Wasim ahmad khanpur

Name -wasim ahamd Father name- zubair ahamd mother name- Phool bivi DOB- 21-11-1991 birth place- Muzaffarpur Bihar Village name khanpur six brother

Heading text
wasim ahamd --Wasim ahmad khanpur (talk) 08:38, 11 February 2015 (UTC)

title: User:Wasim ahmad khanpur


text:
User:Munna Suprathik

= MUNNA SUPRATHIK = A ray of an idea leads a spectrum of opportunities

-Munna Suprathik

I am a web developer, gamer, and student. My interests range from game to blogging, WordPress and video editing. I am also interested in technology, web development, blogging, WordPress, and photography.

title: User:Munna Suprathik


text:
Wikipedia:Articles for deletion/Cascade Framework

The result was   no consensus. Ged UK  13:29, 4 March 2015 (UTC)

Cascade Framework

 * – ( View AfD View log  Stats )

This article (and a related one, John Slegers, that I redirected here) seem to have been pulled apart, but fundamentally there just doesn't appear to be the required coverage in sources to be able to write a decent article on this. I found one source that mentioned it in relation to the Blackberry, but that was only a fleeting mention. There doesn't seem to be much else. Ritchie333 (talk) (cont)  21:34, 10 February 2015 (UTC)
 * Note: This debate has been included in the list of Computing-related deletion discussions. • Gene93k (talk) 19:55, 11 February 2015 (UTC)
 * Note: This debate has been included in the list of Internet-related deletion discussions. • Gene93k (talk) 19:56, 11 February 2015 (UTC)
 * Note: This debate has been included in the list of Software-related deletion discussions. • Gene93k (talk) 19:56, 11 February 2015 (UTC)

 Relisted to generate a more thorough discussion so a clearer consensus may be reached.

Please add new comments below this notice. Thanks, Missvain (talk) 05:29, 17 February 2015 (UTC)

 * Oppose Seem to meet general notability guidelines for websites, more so than most websites on Wikipedia in my opinion.  Royal Mate1  20:14, 18 February 2015 (UTC)

 * Keep - and  (both already referenced in the article) seem to contain the coverage the nom is looking for. ~KvnG 05:22, 22 February 2015 (UTC)
 * Those both look like self-published sources. Anyone can start a website and state a positive or negative opinion about anything - there's no indication that somebody with an impartial view decided it was of any importance. I take a laxer approach to self-published sources than some, for example this site is in my view acceptable for citing serial numbers and content of singles and LPs, but even then, I could not use that source to demonstrate notability. Ritchie333 (talk) (cont)  12:54, 22 February 2015 (UTC)
 * They are not personal blogs and the postings are attributed, not posted by readers; Not clearly WP:SPS in my book. Sources like these is how information now spreads on fast-moving tech topics like this. ~KvnG 21:12, 22 February 2015 (UTC)
 * The Code Geekz site appears to try and be a comprehensive site, but I can't see any obvious source from outside the development community that treats it as important as reliable. Furthermore, one source is just a roundabout of CSS Frameworks, devoting a mere paragraph to it among several others. Since code geekz appears to be trying to documenting everything, irrespective of whether or not the wider non-developer world claims any importance over it, I don't think we would be able to prove any notability from it. Ritchie333 (talk) (cont)  13:04, 24 February 2015 (UTC)
 * Why do you think we need to find sources from "outside the development community?" I consider a paragraph in a roundup from a WP:RS to be WP:SIGNIFICANT coverage. I don't understand what disqualifies this. I don't understand what you find in WP:RS that disqualifies Codegeekz. ~KvnG 15:41, 24 February 2015 (UTC)
 * You haven't made any edits to the article in the two weeks the AfD has been left open. Therefore I assume you are more interested in arguing than improving articles. Goodbye. Ritchie333 (talk) (cont)  17:13, 24 February 2015 (UTC)

 Relisted to generate a more thorough discussion so a clearer consensus may be reached.
 * Delete, per Ritchie333 comments about sources above. Sandy Georgia  (Talk) 13:33, 24 February 2015 (UTC)

Please add new comments below this notice. Thanks, N ORTH A MERICA 1000 00:09, 25 February 2015 (UTC)
 * Delete- software article of unclear notability, lacking significant coverage in reliable sources. Softpedia and bin press are download sites and thus not independent. The rest of the references provided in article are from the developers, blogs, or incidental mentions. The codegeekz.com ref above is a borderline ref, but on its own insufficient to establish notability even if it were solid WP:RS.Dialectric (talk) 20:17, 25 February 2015 (UTC)


text:
George Campbell Deane

Sir George Campbell Deane was the Chief Justice of the Gold Coast Colony from 1929 until 1935. He took the office from Sir Philip Crampton Smyly in 1929 and was succeeded by Sir Philip Bertie Petrides in 1936.

title: George Campbell Deane


text:
Pokémon the Series: XY Kalos Quest

Pokémon the Series: XY Kalos Quest is the eighteenth season of the Pokémon anime series, and the second season of Pokémon the Series: XY, known in Japan as Pocket Monsters: XY (ポケットモンスター エックスワイ). It originally aired in Japan from November 6, 2014, to October 22, 2015, on TV Tokyo, and in the United States from February 7 to December 19, 2015, on Cartoon Network.

Set in the Kalos region, the season follows the adventures of the Pokémon trainer Ash Ketchum, Serena, Clemont and his sister Bonnie as Ash and his Pikachu collect Gym Badges to compete in the Kalos League and as Pokémon Performer Serena wins Princess Keys from Pokémon Showcases so she can enter the Pokémon Showcase Master Class.

The episodes were directed by Tetsuo Yajima and produced by the animation studio OLM.

This is the only dubbed Pokémon season whose subtitle is used only in the DVD releases and not used within the episodes' openings themselves (excluding the first two seasons, referred to simply as "Pokémon" during their first original airings).

Music
The Japanese opening songs are performed by Yusuke Kaiji for 6 episodes, and  performed by Tomohisa Sako for 39 episodes. The ending songs are performed by Shoko Nakagawa for 19 episodes, "Roaring All-Stars" (ガオガオ・オールスター) performed by Little Glee Monster for 26 episodes, and the English opening song is "Be a Hero", performed by Ben Dixon and The Sad Truth, featuring composer Ed Goldfarb. Its instrumental version serves as the ending theme.

Home media releases
Viz Media and Warner Home Video have released the series in the United States on two three-disc volume sets.

The first volume was released on July 12, 2016, and contains 22 episodes and the second was released on December 13, 2016, and contains 23 episodes.

title: Pokémon the Series: XY Kalos Quest


text:
User:Drique Lockhead

Drique; Rapper,Owner Of Lockhead Clothing and CEO of Greenhouse Records, Born Rodrique McIntyre a local East St. Louis, Illinois & St. Louis, Missouri Music Production/Recording Company. Drique’s mom was in the military, which meant that Drique was traveling everywhere. He was born in Germany and every since then he basically been on the road; Learning and growing from the different cultures and people. Going place to place around the world; coast-to-coast, until now where he lives in St. Louis.

Hip-Hop is the genre with no rules, no standards, and more than one way about it. It’s everywhere.” Drique is in the rap game to change it, one step at a time he’s getting closer to the top. as seen on

title: User:Drique Lockhead