jonathan kemp

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
**Life versus Object. Comrade Things and Alien Life: Stack Frame Heap** 

{{:leuphana:stack.jpeg?300|}}

{{:leuphana:sfh1.png|}}

====== Preamble: ======

how the symbolic (thought, inscription) enters into or is executed and embedded within landscape
and how the earth détourns/mirrors these inscriptions – that the operation of chemical, symbolic/logic, and electromagnetic are folded in and out of computation and matter is loosened from readily available modes of composition.

====== What: ======

Stack, Frame, Heap (SFH) is a series of interventions within the mined or damaged environment, attempting to impose logical or computational structures and production processes (underlying these) on this geological landscape.

SFH re-situates some of computation's production processes (etching, leaching, doping) and products within ruined quarries, mines and/or suitable derelict landscapes. Research will also centre on bi-directional parallels between computation and geological metaphors (sedimentation, read write, sort operations) 

vs.

Stack, Frame, Heap is a series of interventions within the mined or damaged environment, attempting to impose logical or computational structures on this geological landscape. Re-animating the disjuncture of nature and pysche (animism), selected computational substrates and refining by-products will be re-interred or returned into the earth (in nature), sparse insertions of computationally derived (component, process) products will sited within the landscape (pits, mines, field) and nurtured over time. 

===== stack/heap/frame in computation=====

A clearer understanding of stack, heap, frame in terms of computation:

An idealised stack, heap, frame: http://www.dcs.warwick.ac.uk/research/modelling/other/eden/advanced/notes/stack.html

Call stack: http://en.wikipedia.org/wiki/Call_stack

Stack (dynamic process) is made up of stack frames for each subroutine/function call when it is called (so there is really a stack of stack frames). Heap (allotted) is for arrays and static variables. Both are in contiguous memory and the stack can grow down to merge/leak into the heap.

See also: http://lambda.uta.edu/cse5317/notes/node33.html and:

http://www.linuxjournal.com/article/6391


===== How we go further with these terms? =====


eg. stack protection from stack smashes by stack canaries (mining) - used to detect a stack buffer overflow before execution of malicious code can occur - see howto bypass them eg.http://phrack.org/issues.html?issue=56&id=5 && mushrooms/similar (shellfish) indicators/asorbers of toxins

Stack overflowing/manipulation and how this can be used to execute malicious code/shift the site of execution. (how?)

Stack overflow: The most common cause of stack overflow is excessively deep or infinite recursion. (also creating large local variables).


====== Why: ======

**[rewrite as sense]**

Insertions proposed as clocking technology's acceleration of discontinuity between, and destabilisation of, thought, human certainty, and matter (for example, that gold can only be understood as any one sensuous (exclusive) object emergent under distinct framings).

This lack of ontological certainty can be further charged as being both a necessary and nihilistic (truth) which under/overmine notions of cybernetic (control). 

Outside any operative (representative) diagrammatic (ontological stability) materiality is seen here as crucially
dependent on the how of its enactment, on the execution of specific material-discursive cuts with their attendant exclusions (waste). 

Through deeper experimental excavation into computational substrates combined with the heaping of its matter on 
matter, a logic of a skewed exclusion is highlighted by the project with the aim of re-emphasising the
_necessary_ contingency thought has over matter (thus updating recent debates in Speculative Realism and the 
like), and, further, re-characterizing through practice any discussion of (im)permaculture and technological 
autophagia.

 
{{:leuphana:sfh3.gif?600|}}


====== Methodology: ======


Production will be centred on the reconfiguration and re-situating of some of computation's 
production processes (etching, leaching, doping) and products within ruined quarries, mines and/or suitable 
derelict landscapes. Research will also centre on bi-directional parallels between computation and geological 
metaphors (sedimentation, read write, sort operations). For example, stack and heap refers both to a 
visualisation of methodologies of memory management within a processor, and to  techniques of mining 
(eg. heap leaching) which refine minerals in situ, forming the material basis of such computation. 

{{:leuphana:sfh4.png?400|}}

**[rewrite below in light of recent methodology notes]**

In situ insertions are planned in derelict mines/quarries, (where the geology of the site provides 
scope for provoking and exciting reactions between component mixes (indigenous and alien to the site). Collected 
elements (mineral substrates, metals ores, computer components) will be processed in operations that:)

reactions between various alien/in situ minerals/elements are provoked through the
actions of: 




  *__sort__  by heat, chemical and mechanical processes in order to 
  *__expose__ them as further sites of excitation in stacks and heaps (over/underground), subject to
  *encourage __flows__  and _channeling_ (miming the processor)(of currents, of liquids) through insertion of impermeable layers (leach pads), 
 

and imposed on the site as stacks (ordered layers), heaps (disordered piles), and frames (defined processes 
including extractions)



processes which are to be encouraged include:

- weathering, growing certain plants, leaching of minerals (bacterial), precipitation/crystallisation, 
generation of electric currents/energy in the earth (telluric, atmospheric, earth battery, photonic, thermo, 
kinetic-piezoelectric), storage of resources/memory)


Heaped deposits include saltpeter beds; sodium chloride brine stacks/seeps; rain sodden iron oxide, calcium 
sulphate, ferrous sulphate heaps, entrained with cyanobacteria; pyrites/copper sulphide minerals piled in open air; ferric sulphate layered over chalcopyrite; slime fillings of more sodium chloride, water, copper sulphate, and mercury; supplemented through: 

  ***natural weathering**
  ***distorted hydroponics** (entrainment (natural/artificial) of flora on carbonate, silicate platelets) 
  ***dissolution** (leaching of mineral/metals in solutions by flora/fauna eg. of chalcopyrites, pyrites with thiobaccilius collected in mine water; or with fungi over bauxite, Aspergillus niger, Penicillium simplicissimum 
  ***precipitation** of solutes (above and below the earth) 
  ***energy transformations/transductions** through magnetic field generation using telluric electrolysis/transmission (grids of copper and zinc antennae), 
  *effecting **thermoelectric** environmental peltier effects in layers of ore (eg. manganese silicate)  → where warmer and colder diffrentials affect fauna growth (and act as crude cloud detector) (playback of magnetotelluric fields)

{{:leuphana:a5chh8uciaazrah.jpg?400|}}

====== further ======

that this can be defined as some kind of bootstrapping - an imposition on the site and a manipulation of certain favourable conditions

and how these changes are rendered visible: plant indicators, a measurement which is part of the earth and becomes an expression acting on itself, some kind of probe/display

====== demonstrations/field notes/experiments ======

====== misc images ======

{{:leuphana:stack1.jpeg|}}

mud computing
jonathan kemp

User Tools

Site Tools

Page Tools
