Phenomenology and building Essay Example | Topics and Well Written Essays - 1750 words

Phenomenology and building - Essay Example Thesis Statement: The purpose of this paper is to write a phenomenological account of Le Corbusier’s Chapelle Notre-Dame du-Haut at Ronchamp. This account emphasizing the qualities of one’s personal experience of the feelings, images and emotions evoked by the building will be related to its material, form and spaces. Le Corbusier states that â€Å"the purpose of architecture is to move us. Architectural emotion exists when the work rings within us in tune with a universe whose laws we obey, recognize and respect† (Fortkamp 39). Similarly, according to Heidegger’s (1962) theory underscoring the phenomenology of built spaces, â€Å"there is no being apart from a world, rather there is first and only a Being in the world† (Seamon 248). Norberg-Schulz (1971), Relph (1976) and other theorists have identified modes of spatial experience as evident in a loose, continuous occurrence ranging from the abstract, measured geometric space to the concretely experienced space of daily living referred to as lived space. Unlike Plato and Euclid’s conceptualization of geometry as the science of space, the phenomenological perspective considers geometric space as having â€Å"a powerful predictive capacity rather than any superior claims to truth† (Seamon 248), while perspectives and impressions of the lived space of the life world form the actual reality. The history of the site as well as that of the earlier predecessor buildings catalysed the creative imagination of Le Corbusier into developing the building as it now exists (Figure 1). The Chapelle Notre-Dame du-Haut at Ronchamp is a chapel of pilgrimmage located at an ancient pilgimmage site, standing on a hill above the village of Ronchamp on the southern edge of the Vosges mountains in France. The present building is used for religious purposes by the clergy. Le Corbusier’s mind took inspiration from an ancient era of human antiquity to create the

Save water Essay Example for Free

Save water Essay WATER SAVINGS PROTOCOL ROLES AND RESPONSIBILITIES Final Version 3.0 June 2009 Acknowledgements This document has been prepared by the Department of Sustainability and Environment in collaboration with Goulburn-Murray Water, the Northern Victoria Irrigation Renewal Project (NVIRP) with technical advice provided by Hydro Environmental. -i- TABLE OF CONTENTS 1. Introduction _______________________________________________________ 1 2. Purpose of this Document ___________________________________________ 2 3. Roles and Responsibilities ___________________________________________ 2 3.1. Project Proponent _____________________________________________________3 3.2. Water Corporation _____________________________________________________4 3.3. Resource Manager_____________________________________________________4 3.4. Minister for Water and Associated Departments ______________________________5 3.4.1. Department for Sustainability and Environment ______________________________ 5 3.5. Minister for Planning and Community Development and Associated Departments ____6 3.6. Minister for Environment and Associated Departments _________________________6 3. 6.1. Catchment Management Authorities (Environmental Managers) _________________ 6 3.7. Murray-Darling Basin Authority ___________________________________________7 4. High Level Process Diagram for Assessing Water Savings ________________ 7 ii 1. Introduction This document â€Å"Roles and Responsibilities† is part of the â€Å"Water Savings Protocol for the Quantification of Water Saving Projects† (the Protocol). The Protocol is a series of documents, which together, provides transparency, and consistency in the estimation and allocation of water savings derived from irrigation modernisation projects. It has been developed based on the key principles in the Draft Northern Region Sustainable Water Strategy and is applicable State-wide. The Protocol consists of: †¢ Technical Manual for the Quantification of Water Savings †¢ Roles and Responsibilities †¢ Water Savings Audit Process The documents that make up the Protocol is shown in Figure 1. WATER SAVINGS PROTOCOL FOR THE QUANTIFICATION OF WATER SAVINGS FROM IRRIGATION MODERNISATION PROJECTS Explanatory Note from the Minister Technical Manual For Quantification of Water Savings Roles Responsibilities Water Savings Audit Process Figure 1: Water Savings Protocol documents The overall purpose of the Water Savings Protocol documents, including this document, is to: †¢ specify a reliable and repeatable process and method to estimate water savings from irrigation modernisation projects; -1- †¢ †¢ 2. provide the best estimate of water savings for inclusion in economic assessments of investments in irrigation modernisation projects; and establish a transparent process which can be readily audited and reported on to enable actual water savings to be converted to entitlements at an appropriate time. Purpose of this Document The purpose of this document is to set out the roles and responsibilities of the stakeholders involved in irrigation modernisation projects. The roles and responsibilities are specifically related to the accounting, reporting and auditing of associated water savings. These roles and responsibilities are consistent with Government Policies including the legislated roles and responsibilities of the various organisations in the Water Act 1989 and the Environmental Effects Act 1978. 3. Roles and Responsibilities The following sections outline the specific roles and responsibilities of the various organisations involved in water savings projects. These organisations include:i. the Project Proponent ii. the System Operator iii. the Minister for Water iv. the Department of Sustainability and Environment (the Department) v. Environmental Regulator (Minister for Planning) and Associated Departments vi. Minister for Environment and Associated Departments vii. Environmental Manager (Catchment Management Authority and/or Parks Victoria) viii. the Murray-Darling Basin Authority (in relation to Northern Victoria). The relationship between the above mentioned organisations and their involvement in water savings projects throughout Victoria can be seen schematically in Figure 2. -2- Minister for Environment and Climate Change Minister for Planning and Community Development Catchment Management Authorities Water Corporation Parks Victoria Minister for Water Resource Manager / System Operator Department of Sustainability and Environment Murray Darling Basin Authority Project Proponent Figure 2: Victorian Water Savings Projects – Key Organisations 3.1. Project Proponent The project proponent is the entity with the role of planning, designing and delivering the irrigation modernisation project including its various water savings interventions. The role of the Proponent is to: †¢ identify water saving opportunities. †¢ devise and develop the scope of projects in conjunction with the holder of the system operating water entitlement. †¢ seek all necessary approvals to works and endorsement of their associated water savings. †¢ identify potential environmental impacts and mitigation measures and consult with the appropriate environmental managers at a State and Federal level. †¢ quantify the volume of water savings to be generated by each intervention in accordance with the methodology outlined in the Technical Manual for the Quantification of Water Savings. †¢ prior to implementing the annual works program, and at reasonable intervals throughout the season if requested by the System Operator, calculate the estimated interim water savings for the current/future irrigation season for the purpose for setting this water aside for future allocation. †¢ communicate to the System Operator, the planned annual works program and changes as they occur. †¢ implement works in accordance with the works program. -3- †¢ communicate any significant departures from the planned works program, as it is implemented, to the System Operator. †¢ notify the System Operator and the Executive Director of Water Entitlements and Strategies (within the Department) of the volumes of water that are expected to be set aside (Interim Savings) and transferred (Long Term Savings) as result of each intervention being implemented. †¢ calculate the actual water savings arising from the works in accordance with the Technical Manual for the Quantification of Water Savings to determine both the interim and the long term water savings. †¢ report, as required, the projected interim and final water savings including any details of changes from the overall targeted volumes of water savings for the project or water savings intervention. †¢ arrange for an independent audit and report of the water savings utilising the independent auditor(s) awarded to the auditing of water savings by the independent panel in accordance with the Audit Process. †¢ advise the System Operator and Executive Director of Water Entitlements and Strategies (within the Department) on the outcomes of the water savings audit 3.2. Water Corporation The Water Corporation is responsible for assessing system losses on the longer term to ensure longevity of water savings realised through interventions associated with irrigation modernisation projects. The System Operator is to: †¢ ensure water delivery services can continue to be provided to water entitlement holders on the system. †¢ on the advice of the proponent, consult with system water users impacted by the agreed project works. †¢ provide water system asset information required to enable the Project Proponent to complete interim and long term water savings projections. †¢ apply to Minister for Water to amend/transfer part of the savings as water entitlement. †¢ operate and maintain the water delivery system in accordance with the agreed project objectives and ensure accountable water savings are sustainable and maintained in the long term. 3.3. Resource Manager The Resource Manager or Storage Operator, as defined in the relevant bulk entitlements, is responsible for managing and allocating the water resources in accordance with the bulk entitlements. This includes making and projecting seasonal determinations. The Resource Manager / Storage Operator is to: †¢ provide to the proponent, projections of annual water deliveries and allocations to enable the progressive calculation of interim water savings as the project is implemented. -4- †¢ manage and collect water delivery system flow (inflow and outflow) measurement data and make that data available t the Project Proponent. †¢ ensure provision of water related data to the Project Proponent and the Department is guaranteed through a quality assurance process. Where the data has been modified or filtered, provide both the raw and modified data including documentation of reasons for modification. †¢ at the start of each irrigation season, or progressively as agreed, set aside the amounts of water projected to be saved through the modernisation works. †¢ confirm the estimates of actual water savings provide by the Project Proponent and where necessary recommend an amendment to those savings for consideration by the Project Proponent. 3.4. Minister for Water and Associated Departments The Minister for Water is responsible for the water portfolio in the State of Victoria. The Minister oversees the policy direction with the support of the Department. The delivery of long term water savings and ensuring government water savings targets are met is a key responsibility of the Minister. The Minister for Water: †¢ has agreed to the Water Savings Framework and its associated Water Savings Protocols including its Technical Manual for the Quantification of Water Savings and the Water Savings Audit Processes †¢ will, with the support of the Department, update the Protocol to ensure continual improvement and the use of the best technical basis available at the time. †¢ will, with the support of the Department, amend and transfer Bulk entitlements (Water Act 1989) to represent the long term water savings realised through the modernisation program. 3.4.1. Department for Sustainability and Environment The Department supports the Minister for Water in the administration of the water portfolio in Victoria with respect to water recovery. The Department will: †¢ support the Minister for Water in developing a Technical Manual for the Quantification of Water Savings (Attachment 1) and the associated Audit Processes (Attachment 3). †¢ support the Minister for Water in amending and transferring bulk entitlements. †¢ recommend to the Minister for Water updates to the Protocols, particularity the Technical Manual for the Quantification of Water Savings to ensure continual improvement and the use of the best technical basis available at the time. †¢ convene a meeting with the System Operator and the Project Proponent and Department a minimum of every 6 months to review the application of the Technical Manual for the Quantification of Water Savings in Northern Victoria. -5- †¢ arrange for a Panel to establish a list of independent auditors which may be used to audit water savings estimates and related baseline data (both interim savings on annual basis and long term savings at the end of the water savings project). †¢ establish an agreed methodology for calculating the annual Long Term Cap Equivalent (LTCE) conversion factor to be used in long term water savings estimates. †¢ provide the Project Proponent (and System Operator if requested) with the Long Term Cap Equivalent conversion factors for particular years. 3.5. Minister for Planning and Community Development and Associated Departments The Minister for Planning and Community Development oversees the adherence of water savings projects to all relevant environmental legislation (both State and Federal). The Minister for Planning and Community Development will: †¢ assess environmental impacts of the works and measures proposed by the Project Proponent †¢ provided certain conditions are met, issue planning approvals for the works proposed by the Project Proponent (it should be noted that it is not the role of regulator to quantify the volume of water savings). 3.6. Minister for Environment and Associated Departments The Minister for Environment is responsible for management and mitigation of any undesirable impacts of the water savings project. The Minister for Environment has a responsibility to: †¢ work with environmental managers to consult on any potential environmental impact of works and seek multiple benefit projects †¢ provide advice to the Minister for Planning and Community Development on potential environmental impacts associated with works †¢ develop the principles for the planning and use of Requisite (Mitigating) Water to ensure net environmental gain to the project region. 3.6.1. Catchment Management Authorities (Environmental Managers) The Catchment Management Authorities (CMAs) have a charter to develop and oversee the implementation of Regional Catchment Strategies aimed at improving or at least maintaining catchment health and to, on behalf of the Minister for Environment, manage the environmental water entitlements. The role related to the environmental water entitlement includes: †¢ improving river and wetland health through the use of the Environmental Water Reserve and delivery of complementary works. †¢ working with the water savings Project Proponent to identify potential environmental impacts of the actions and potential mitigation measures proposed by the Project Proponent. -6- †¢ working with the Project Proponent and System Operator to seek multiple benefit projects and multiple project benefits. In instances where Parks Victoria is the owner or custodian of the land, the catchment responsibilities for the maintenance of catchment heath will be delivered through Parks Victoria. 3.7. Murray-Darling Basin Authority The Murray-Darling Basin Authority is responsible for integrated, sustainable management of water resources in the Murray-Darling Basin. Its role includes: †¢ ensuring appropriate water diversion accounting against the Murray-Darling Basin Cap on allowable annual diversions. †¢ developing and implementing of the Basin Management Plan which will be a strategic plan for the integrated and sustainable management of water resources in the Murray-Darling Basin. Details of the future role of the Authority in relation to water savings will be resolved as part of the Basin Plan. 4. High Level Process Diagram for Assessing Water Savings The quantification of water savings is undertaken in four separate stages or Phases of the water savings project, these phases are defined as follows: †¢ Phase 1: †¢ Phase 2: †¢ Phase 3: †¢ Phase 4: The initial â€Å"Business Case† long term estimates of water savings for the planned program of works The annual pre-works estimates of interim water savings to be set aside within the water savings account. The annual post-works measurement or verification of interim water savings able to be allocated from the water savings account. The end of program assessment of the overall long term water savings achieved through the modernisation program. Each of the Phases, and the steps which are required to quantify the water savings under these Phases, is described in detail within the Technical Manual for the Quantification of Water Savings. Figure 3 schematically describes the roles and responsibilities of the above mentioned organisations in estimating, measuring, verifying, and reporting water savings associated with irrigation system modernisation programs. The interactions between each of the Phases of reporting and the required information sharing are also provided within that diagram. -7- Figure 3: High level process flow for defining, capturing reporting Water Savings in Irrigation Modernisation Project -8-

The Relationship Between Crime and Guns in the United States :: Second Amendment The Right To Bear Arms

The right to bear arms is an American right featured in the second Amendment of the Constitution. In the 18th century when the constitution was written, times were different, there was a need for citizens to arm themselves to insure the safety of the society as a whole. In the modern world, the police department preserves the safety of society and there is no need for citizens to carry weapons. The founding fathers of the Constitution could never have imagined the horrendous outcome of their actions. Every year too many lives are claimed as the result of American's owning an excessive number of firearms. Compared to other western countries that have considerably stricter gun control laws America is still viewed as â€Å"The Wild-Wild West† (ARPP, 66). However, is there a relationship between crime and firearms? In this second amendment our right to have a gun, are we dooming ourselves with higher crime rates and more horrific crimes just to have the right to have a gun in our house? This paper will set forth and find the results of studies conducted to find a conclusion. This is a very important issue when it comes to sociology and our society. The importance of violence and force as sources of power has only recently begun to achieve recognition among sociologists. Power has traditionally been conceptualized as deriving from lasting attributes of persons and from their position in the social structure such as sex and race. However, when power is examined at the interpersonal level it is typically viewed as deriving from family role and gender. These sources of power ultimately derive to some extent from a capacity to use physical force and violence. This capacity often relies partly on a rather transitory attribute of the person, the possession of weaponry. The single most important factor that sets human violence apart from aggression among lower animals is arguably the human’s greater technological capacity to inflict harm on another creature. These â€Å"tools of death† are readily available to humans and are vastly more lethal than even the most deadly natural equipment of any other species (Kleck, 670). Yet, little is known about the impact of weaponry on violence or how weaponry is used to coerce compliance in hostile social encounters. Firearms are seen as violence enhancing devices, it is just assumed that the possession along with the use of firearms increase the chances of the victim to be injured or killed.

Digital Fortress Chapter 59-62

Chapter 59 Susan reached for Commander Strathmore's hand as he helped her up the ladder onto the Crypto floor. The image of Phil Chartrukian lying broken on the generators was burned into her mind. The thought of Hale hiding in the bowels of Crypto had left her dizzy. The truth was inescapable-Hale had pushed Chartrukian. Susan stumbled past the shadow of TRANSLTR back toward Crypto's main exit-the door she'd come through hours earlier. Her frantic punching on the unlit keypad did nothing to move the huge portal. She was trapped; Crypto was a prison. The dome sat like a satellite, 109 yards away from the main NSA structure, accessible only through the main portal. Since Crypto made its own power, the switchboard probably didn't even know they were in trouble. â€Å"The main power's out,† Strathmore said, arriving behind her. â€Å"We're on aux.† The backup power supply in Crypto was designed so that TRANSLTR and its cooling systems took precedence over all other systems, including lights and doorways. That way an untimely power outage would not interrupt TRANSLTR during an important run. It also meant TRANSLTR would never run without its freon cooling system; in an uncooled enclosure, the heat generated by three million processors would rise to treacherous levels-perhaps even igniting the silicon chips and resulting in a fiery meltdown. It was an image no one dared consider. Susan fought to get her bearings. Her thoughts were consumed by the single image of the Sys-Sec on the generators. She stabbed at the keypad again. Still no response. â€Å"Abort the run!† she demanded. Telling TRANSLTR to stop searching for the Digital Fortress pass-key would shut down its circuits and free up enough backup power to get the doors working again. â€Å"Easy, Susan,† Strathmore said, putting a steadying hand on her shoulder. The commander's reassuring touch lifted Susan from her daze. She suddenly remembered why she had been going to get him. She wheeled, â€Å"Commander! Greg Hale is North Dakota!† There was a seemingly endless beat of silence in the dark. Finally Strathmore replied. His voice sounded more confused than shocked. â€Å"What are you talking about?† â€Å"Hale†¦Ã¢â‚¬  Susan whispered. â€Å"He's North Dakota.† There was more silence as Strathmore pondered Susan's words. â€Å"The tracer?† He seemed confused. â€Å"It fingered Hale?† â€Å"The tracer isn't back yet. Hale aborted it!† Susan went on to explain how Hale had stopped her tracer and how she'd found E-mail from Tankado in Hale's account. Another long moment of silence followed. Strathmore shook his head in disbelief. â€Å"There's no way Greg Hale is Tankado's insurance! It's absurd! Tankado would never trust Hale.† â€Å"Commander,† she said, â€Å"Hale sank us once before-Skipjack. Tankado trusted him.† Strathmore could not seem to find words. â€Å"Abort TRANSLTR,† Susan begged him. â€Å"We've got North Dakota. Call building security. Let's get out of here.† Strathmore held up his hand requesting a moment to think. Susan looked nervously in the direction of the trapdoor. The opening was just out of sight behind TRANSLTR, but the reddish glow spilled out over the black tile like fire on ice. Come on, call Security, Commander! Abort TRANSLTR! Get us out of here! Suddenly Strathmore sprang to action. â€Å"Follow me,† he said. He strode toward the trapdoor. â€Å"Commander! Hale is dangerous! He-â€Å" But Strathmore disappeared into the dark. Susan hurried to follow his silhouette. The commander circled around TRANSLTR and arrived over the opening in the floor. He peered into the swirling, steaming pit. Silently he looked around the darkened Crypto floor. Then he bent down and heaved the heavy trapdoor. It swung in a low arc. When he let go, it slammed shut with a deadening thud. Crypto was once again a silent, blackened cave. It appeared North Dakota was trapped. Strathmore knelt down. He turned the heavy butterfly lock. It spun into place. The sublevels were sealed. Neither he nor Susan heard the faint steps in the direction of Node 3. Chapter 60 Two-tone headed through the mirrored corridor that led from the outside patio to the dance floor. As he turned to check his safety pin in the reflection, he sensed a figure looming up behind him. He spun, but it was too late. A pair of rocklike arms pinned his body face-first against the glass. The punk tried to twist around. â€Å"Eduardo? Hey, man, is that you?† Two-Tone felt a hand brush over his wallet before the figure leaned firmly into his back. â€Å"Eddie!† the punk cried. â€Å"Quit fooling around! Some guy was lookin' for Megan.† The figure held him firmly. â€Å"Hey, Eddie, man, cut it out!† But when Two-Tone looked up into the mirror, he saw the figure pinning him was not his friend at all. The face was pockmarked and scarred. Two lifeless eyes stared out like coal from behind wire-rim glasses. The man leaned forward, placing his mouth against Two-Tone's ear. A strange, voice choked, â€Å"Adonde fue? Where'd he go?† The words sounded somehow misshapen. The punk froze, paralyzed with fear. â€Å"Adonde fue?† the voice repeated. â€Å"El Americano.† â€Å"The†¦ the airport. Aeropuerto,† Two-Tone stammered. â€Å"Aeropuerto?† the man repeated, his dark eyes watching Two-Tone's lips in the mirror. The punk nodded. â€Å"Tenia el anillo? Did he have the ring?† Terrified, Two-Tone shook his head. â€Å"No.† â€Å"Viste el anillo? Did you see the ring?† Two-Tone paused. What was the right answer? â€Å"Viste el anillo?† the muffled voice demanded. Two-Tone nodded affirmatively, hoping honesty would pay. It did not. Seconds later he slid to the floor, his neck broken. Chapter 61 Jabba lay on his back lodged halfway inside a dismantled mainframe computer. There was a penlight in his mouth, a soldering iron in his hand, and a large schematic blueprint propped on his belly. He had just finished attaching a new set of attenuators to a faulty motherboard when his cellular phone sprang to life. â€Å"Shit,† he swore, groping for the receiver through a pile of cables. â€Å"Jabba here.† â€Å"Jabba, it's Midge.† He brightened. â€Å"Twice in one night? People are gonna start talking.† â€Å"Crypto's got problems.† Her voice was tense. Jabba frowned. â€Å"We been through this already. Remember?† â€Å"It's a power problem.† â€Å"I'm not an electrician. Call Engineering.† â€Å"The dome's dark.† â€Å"You're seeing things. Go home.† He turned back to his schematic. â€Å"Pitch black!† she yelled. Jabba sighed and set down his penlight. â€Å"Midge, first of all, we've got aux power in there. It would never be pitch black. Second, Strathmore's got a slightly better view of Crypto than I do right now. Why don't you call him?† â€Å"Because this has to do with him. He's hiding something.† Jabba rolled his eyes. â€Å"Midge sweetie, I'm up to my armpits in serial cable here. If you need a date, I'll cut loose. Otherwise, call Engineering.† â€Å"Jabba, this is serious. I can feel it.† She can feel it? It was official, Jabba thought, Midge was in one of her moods. â€Å"If Strathmore's not worried, I'm not worried.† â€Å"Crypto's pitch black, dammit!† â€Å"So maybe Strathmore's stargazing.† â€Å"Jabba! I'm not kidding around here!† â€Å"Okay, okay,† he grumbled, propping himself up on an elbow. â€Å"Maybe a generator shorted out. As soon as I'm done here, I'll stop by Crypto and-â€Å" â€Å"What about aux power!† Midge demanded. â€Å"If a generator blew, why is there no aux power?† â€Å"I don't know. Maybe Strathmore's got TRANSLTR running and aux power is tapped out.† â€Å"So why doesn't he abort? Maybe it's a virus. You said something earlier about a virus.† â€Å"Damn it, Midge!† Jabba exploded. â€Å"I told you, there's no virus in Crypto! Stop being so damned paranoid!† There was a long silence on the line. â€Å"Aw, shit, Midge,† Jabba apologized. â€Å"Let me explain.† His voice was tight. â€Å"First of all, we've got Gauntlet-no virus could possibly get through. Second, if there's a power failure, it's hardware-related-viruses don't kill power, they attack software and data. Whatever's going on in Crypto, it's not a virus.† Silence. â€Å"Midge? You there?† Midge's response was icy. â€Å"Jabba, I have a job to do. I don't expect to be yelled at for doing it. When I call to ask why a multi billion-dollar facility is in the dark, I expect a professional response.† â€Å"Yes, ma'am.† â€Å"A simple yes or no will suffice. Is it possible the problem in Crypto is virus-related?† â€Å"Midge†¦ I told you-â€Å" â€Å"Yes or no. Could TRANSLTR have a virus?† Jabba sighed. â€Å"No, Midge. It's totally impossible.† â€Å"Thank you.† He forced a chuckle and tried to lighten the mood. â€Å"Unless you think Strathmore wrote one himself and bypassed my filters.† There was a stunned silence. When Midge spoke, her voice had an eerie edge. â€Å"Strathmore can bypass Gauntlet?† Jabba sighed. â€Å"It was a joke, Midge.† But he knew it was too late. Chapter 62 The Commander and Susan stood beside the closed trapdoor and debated what to do next. â€Å"We've got Phil Chartrukian dead down there,† Strathmore argued. â€Å"If we call for help, Crypto will turn into a circus.† â€Å"So what do you propose we do?† Susan demanded, wanting only to leave. Strathmore thought a moment. â€Å"Don't ask me how it happened,† he said, glancing down at the locked trapdoor, â€Å"but it looks like we've inadvertently located and neutralized North Dakota.† He shook his head in disbelief. â€Å"Damn lucky break if you ask me.† He still seemed stunned by the idea that Hale was involved in Tankado's plan. â€Å"My guess is that Hale's got the pass-key hidden in his terminal somewhere-maybe he's got a copy at home. Either way, he's trapped.† â€Å"So why not call building security and let them cart him away?† â€Å"Not yet,† Strathmore said, â€Å"if the Sys-Secs uncover stats of this endless TRANSLTR run, we've got a whole new set of problems. I want all traces of Digital Fortress deleted before we open the doors.† Susan nodded reluctantly. It was a good plan. When Security finally pulled Hale from the sublevels and charged him with Chartrukian's death, he probably would threaten to tell the world about Digital Fortress. But the proof would be erased-Strathmore could play dumb. An endless run? An unbreakable algorithm? But that's absurd! Hasn't Hale heard of the Bergofsky Principle? â€Å"Here's what we need to do.† Strathmore coolly outlined his plan. â€Å"We erase all of Hale's correspondence with Tankado. We erase all records of my bypassing Gauntlet, all of Chartrukian's Sys-Sec analysis, the Run-Monitor records, everything. Digital Fortress disappears. It was never here. We bury Hale's key and pray to God David finds Tankado's copy.† David, Susan thought. She forced him from her mind. She needed to stay focused on the matter at hand. â€Å"I'll handle the Sys-Sec lab,† Strathmore said. â€Å"Run-Monitor stats, mutation activity stats, the works. You handle Node 3. Delete all of Hale's E-mail. Any records of correspondence with Tankado, anything that mentions Digital Fortress.† â€Å"Okay,† Susan replied, focusing. â€Å"I'll erase Hale's whole drive. Reformat everything.† â€Å"No!† Strathmore's response was stern. â€Å"Don't do that. Hale most likely has a copy of the pass-key in there. I want it.† Susan gaped in shock. â€Å"You want the pass-key? I thought the whole point was to destroy the pass-keys!† â€Å"It is. But I want a copy. I want to crack open this damn file and have a look at Tankado's program.† Susan shared Strathmore's curiosity, but instinct told her unlocking the Digital Fortress algorithm was not wise, regardless of how interesting it would be. Right now, the deadly program was locked safely in its encrypted vault-totally harmless. As soon as he decrypted it†¦. â€Å"Commander, wouldn't we be better off just to-â€Å" â€Å"I want the key,† he replied. Susan had to admit, ever since hearing about Digital Fortress, she'd felt a certain academic curiosity to know how Tankado had managed to write it. Its mere existence contradicted the most fundamental rules of cryptography. Susan eyed the commander. â€Å"You'll delete the algorithm immediately after we see it?† â€Å"Without a trace.† Susan frowned. She knew that finding Hale's key would not happen instantly. Locating a random pass-key on one of the Node 3 hard drives was somewhat like trying to find a single sock in a bedroom the size of Texas. Computer searches only worked when you knew what you were looking for; this pass-key was random. Fortunately, however, because Crypto dealt with so much random material, Susan and some others had developed a complex process known as a nonconformity search. The search essentially asked the computer to study every string of characters on its hard drive, compare each string against an enormous dictionary, and flag any strings that seemed nonsensical or random. It was tricky work to refine the parameters continually, but it was possible. Susan knew she was the logical choice to find the pass-key. She sighed, hoping she wouldn't regret it. â€Å"If all goes well, it will take me about half an hour.† â€Å"Then let's get to work,† Strathmore said, putting a hand on her shoulder and leading her through the darkness toward Node 3. Above them, a star-filled sky had stretched itself across the dome. Susan wondered if David could see the same stars from Seville. As they approached the heavy glass doors of Node 3, Strathmore swore under his breath. The Node 3 keypad was unlit, and the doors were dead. â€Å"Damn it,† he said. â€Å"No power. I forgot.† Strathmore studied the sliding doors. He placed his palms flat against the glass. Then he leaned sideways trying to slide them open. His hands were sweaty and slipped. He wiped them on his pants and tried again. This time the doors slid open a tiny crack. Susan, sensing progress, got in behind Strathmore and they both pushed together. The doors slid open about an inch. They held it a moment, but the pressure was too great. The doors sprang shut again. â€Å"Hold on,† Susan said, repositioning herself in front of Strathmore. â€Å"Okay, now try.† They heaved. Again the door opened only about an inch. A faint ray of blue light appeared from inside Node 3; the terminals were still on; they were considered critical to TRANSLTR and were receiving aux power. Susan dug the toe of her Ferragamo's into the floor and pushed harder. The door started to move. Strathmore moved to get a better angle. Centering his palms on the left slider, he pushed straight back. Susan pushed the right slider in the opposite direction. Slowly, arduously, the doors began to separate. They were now almost a foot apart. â€Å"Don't let go,† Strathmore said, panting as they pushed harder. â€Å"Just a little farther.† Susan repositioned herself with her shoulder in the crack. She pushed again, this time with a better angle. The doors fought back against her. Before Strathmore could stop her, Susan squeezed her slender body into the opening. Strathmore protested, but she was intent. She wanted out of Crypto, and she knew Strathmore well enough to know she wasn't going anywhere until Hale's pass-key was found. She centered herself in the opening and pushed with all her strength. The doors seemed to push back. Suddenly Susan lost her grip. The doors sprang toward her. Strathmore fought to hold them off, but it was too much. Just as the doors slammed shut, Susan squeezed through and collapsed on the other side. The commander fought to reopen the door a tiny sliver. He put his face to the narrow crack. â€Å"Jesus, Susan-are you okay?† Susan stood up and brushed herself off. â€Å"Fine.† She looked around. Node 3 was deserted, lit only by the computer monitors. The bluish shadows gave the place a ghostly ambiance. She turned to Strathmore in the crack of the door. His face looked pallid and sickly in the blue light. â€Å"Susan,† he said. â€Å"Give me twenty minutes to delete the files in Sys-Sec. When all traces are gone, I'll go up to my terminal and abort TRANSLTR.† â€Å"You better,† Susan said, eyeing the heavy glass doors. She knew that until TRANSLTR stopped hoarding aux power, she was a prisoner in Node 3. Strathmore let go of the doors, and they snapped shut. Susan watched through the glass as the commander disappeared into the Crypto darkness.

How smart are sheep? Essay

How Smart Are Sheep by Barbara Drake is about the intelligence of sheep and the studies that have been conducted to prove that sheep can feel different emotions and recognize dogs and humans as their enemies. Evolution has re-wired the sheep brain to know to hate and stay away from humans and dogs. Brain activity research in sheep has shown that sheep see dogs and humans as more alike than comparing the human and the dog to themselves. Drake explains that â€Å"Of course, fro ma distance, if a human being gets down on all fours, there is little uncertainty and the sheep’s brain may start sending ‘possible other sheep’ signals until the sheep gets close enough to realize its mistake† (247). Research has also found that sheep have emotions. They have been known to feel and display moods of fear and happiness. For example: when sheep see an approaching human they will start to feel fearful or if an approaching human is carrying a bag of grains for them to eat then they will start to feel happy because they know that they are about to eat. Drake believes that people who believe that animals do not have feelings or emotions are just trying to find an excuse not to feel bad about the horrible things that we do to animals to be able to harvest their bodies for food. â€Å"If a creature has no feelings, it can feel no pain,† Drake explains is the common clichà © phrase that humans use to make themselves feel better about the harmful things we do to animals as a society (248). The feeling of happiness sheep feel when a human is bringing them food is not because of the human, but it is that the human is bringing them. Bummer lambs, which cannot be brought up by their mothers, are bottle-fed and are most commonly known to display happy emotions when their bottles are being brought to them. The bummer lambs start to become hostile and resentful when it’s human starts to wean it from its bottle. Drake has â€Å"seen weaned bummers use a resentful kind of body language that can only be called sulking† (248). This kind of behavior is the beginning of the behavior that has naturally been wired into their brains to dislike humans. Other research shows that sheep produce more excitable brainwaves when being shown a picture of horned sheep. If a sheep is shown a picture of a sheep upside down it will not recognize the sheep because, usually, sheep are only recognizable on all fours. Drake states, â€Å"In fact, a sheep on its back is liable to be in trouble† (249). Sheep have been categorized as stupid because of their  strong herding instincts. Entire herds of sheep have been known to walk off of cliffs just because their leader went off first. Sheep were tested below the intelligence level of horses and cattle when presented a bucket of feed that was covered in in a black cloth. It took the sheep more than several tries to figure out that the cloth has to be removed to retrieve the food. Another test showed that in single-trial learning, sheep knew how to recognize a plant they shouldn’t eat after only eating it once. Lambs also learn this by example from their mothers. Sheep also know to go into their pens at night and how to sort themselves into the ram and ewe sides of the pen. Drake encountered an eight-month old lamb that was lost and was trying to find its way home. Not sure where the lamb belonged, Drake sold the lamb to some people who lived on the other side of town. A few weeks later the lamb had gone missing. The lamb had panicked and jumped the fence because it had been left all alone in the pen by itself. â€Å"This time when the new owners returned the lamb to their farm, they made sure there were a couple of ewes waiting for them in the pen,† Drake explained, concerning the lamb that had escaped (251).