The following warnings occurred:
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined array key "avatartype" - Line: 783 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 783 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined variable $awaitingusers - Line: 34 - File: global.php(844) : eval()'d code PHP 8.0.30 (Linux)
File Line Function
/global.php(844) : eval()'d code 34 errorHandler->error
/global.php 844 eval
/printthread.php 16 require_once
Warning [2] Undefined array key "style" - Line: 909 - File: global.php PHP 8.0.30 (Linux)
File Line Function
/global.php 909 errorHandler->error
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$lang_select_default - Line: 5010 - File: inc/functions.php PHP 8.0.30 (Linux)
File Line Function
/inc/functions.php 5010 errorHandler->error
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined array key "additionalgroups" - Line: 7045 - File: inc/functions.php PHP 8.0.30 (Linux)
File Line Function
/inc/functions.php 7045 errorHandler->error
/inc/functions.php 5030 is_member
/global.php 909 build_theme_select
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(257) : eval()'d code PHP 8.0.30 (Linux)
File Line Function
/printthread.php(257) : eval()'d code 2 errorHandler->error
/printthread.php 257 eval
/printthread.php 117 printthread_multipage
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error
Warning [2] Undefined array key "showimages" - Line: 160 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 160 errorHandler->error
Warning [2] Undefined array key "showvideos" - Line: 165 - File: printthread.php PHP 8.0.30 (Linux)
File Line Function
/printthread.php 165 errorHandler->error



BAJR Federation Archaeology
single context system-bogs dollox or nightmare? - Printable Version

+- BAJR Federation Archaeology (http://www.bajrfed.co.uk)
+-- Forum: BAJR Federation Forums (http://www.bajrfed.co.uk/forumdisplay.php?fid=3)
+--- Forum: The Site Hut (http://www.bajrfed.co.uk/forumdisplay.php?fid=7)
+--- Thread: single context system-bogs dollox or nightmare? (/showthread.php?tid=1899)

Pages: 1 2 3 4


single context system-bogs dollox or nightmare? - the invisible man - 3rd June 2005

At the risk of being pedantic.... given that a Molas sheet covers one 5m grid square, that being the idea of it, and grid north is always up you only need to give the reference in one corner (SW) and everything is located. Strictly speaking you don't even need to do that as there's a space on the top for you to write the grid square in e.g 115/215.

One would draw a section of a ditch, or perhaps an intereseting pit.

I recall someone carefully doing a multicontext plan of a trench at 1:75 scale. No-one knew till afterwards.

Today, Bradford. Tomorrow, well, Bradford probably.


single context system-bogs dollox or nightmare? - Curator Kid - 3rd June 2005

I always wrote the (single) context number of the feature in the top right-hand corner, as this also acted as the plan number (as Achingknees says). The completed sheets should always be filed by grid square rather than context number, so there's no need for the extra a's & b's to mark the feature going over grid squares - it's only a single plan - just on 2 or 3 sheets. When it comes to post-ex, this means that you can divvy out 5m squares to people to work on the plans & matrices, and then just coordinate the results and tie them together when they are finished. Teaching people about sub-grouping, matrices and post-ex good practice is a lot easier when only a single grid square is involved.

Everything should be planned at the same scale - most likely 1:20 on an urban stratified site - or else the overlays don't work properly. Sections & elevations as appropriate, and these require a register to keep track of them - all cross-referenced onto the context sheets. And the supervisor MUST check the records as work goes along - if someone's mucking their square(s) up or not properly working in tandem with the diggers in adjacent squares it can all go pear shaped! Very rarely any need to plan fills, but annotated sketches on sheets to bung levels on are most important...


single context system-bogs dollox or nightmare? - BAJR Host - 3rd June 2005

Damn...... I had jsut written a long reply.... got phoned by a developer... ("oh.... I seemed to have demolished half a farm!") then I get back here and you took the words out of my mouth!

curse you Curator Kid!



Another day another WSI?


single context system-bogs dollox or nightmare? - Curator Kid - 3rd June 2005

Awww - sorry Mr. Hosty! The developers are eerily quiet today (only one scare about a Scheduled site possibly being dug up so far!). This usually spells trouble for next week though. Or one of those sad 'phone calls - "we're starting work on Monday - can we send you the WSI to approve this afternoon" from a unit manager at 4.30 on a Friday...

(Answer's "no you're not and no you can't" by the way if any unit managers are reading this...)



single context system-bogs dollox or nightmare? - achingknees - 3rd June 2005

ooh mr invisible - you're one big pedantSmile

1:75?!? - bloody bonkers!

Curator Kid - agree with you on the training value of one square only, but important on site and in post ex to see the bigger site, how all the squares work together, and how to group features/deposits aiming for phasing. Of course this all comes together in your cosy mutual matrix :face-approve:

back on me head...


single context system-bogs dollox or nightmare? - Curator Kid - 3rd June 2005

Couldn't agree more Achingknees. For the diggers on a site, the important thing is to properly atomise the site and make sure their records are fully completed. Post-ex is then for putting it all back together again. A good supervisor should be able to maintain control of all this, whilst keeping a good grasp on the wider picture, and hopefully keeping everyone else in touch with the basics of what is going on overall.

A complicated matrix, that really works and describes the site properly with no spurious gaps or dodgy relationships, is a marvellous thing of beauty.


single context system-bogs dollox or nightmare? - troll - 5th June 2005

Aforesaid supervisor could have wings, a halo and, a harp but, can`t do justice to a site when project designs/method statements and time budgets are estimated and prepared by grown ups who quite often-completely miss the point. We can do our jobs on the ground under pressure if the project is prepared properly- Supervisors and above have enough to do without having to allow for indifferent and quite often-absurd research.Big Grin


single context system-bogs dollox or nightmare? - deepdigger - 8th June 2005

Too true Troll, but to answer the original Question, yes i like it. Its simple in most cases, easy to describe and effective too.
So yes it is the "mutts nuts"!!

deep