OpenLLM-France/wikimedia huggingface dataset:
# Australian History/Colonialism

‹ Return to the Contents ‹ Back to Explorers After Cook
There were a number of factors which led to the Colonisation of Australia.

### In this Chapter

* Settlement of New South Wales (1788-1889) ›
* Van Diemen's Land (Tasmania) (1825-1889) ›
* Swan River (Western Australia) (1829-1889) ›
* South Australia (1836-1889) ›
* Victoria (1850-1889) ›
* Queensland (1859-1889) ›
* Forward to The Road to Federation ›
# Australian History/Introduction

‹ Return to the Contents ‹ Back to the Preface
While Australia is a young nation, its development over a period of little more than two centuries has been rapid and remarkable.
This book is a social, cultural, political, economic, and military history of Australia covering the nation's history from the continent's pre-European era through to the present day. It focuses on the early history of the Colonies and key events in their history prior to Federation, as well as each of the decades - since Federation - to the present day.
Forward to the First Settlers ›
# Bards Bluegrass Fiddle Tunebook Supplement

* Blue Moon of Kentucky
* Can the Circle Be Unbroken (By and By)
* Cotton Fields
* Orange Blossom Special
* Rocky Top
* Uncle Pen
* Bill Monroe discography
* Molly and Tenbrooks
* When My Blue Moon Turns to Gold Again

## Resources

* Meta Bluegrass

## Other Wikibooks of interest

* Compendium of Fiddle Styles
* How to Play Fiddle
* Ethnography of Fiddle
* Bards Old Time Fiddle Tunebook Supplement
* Bards Irish Fiddle Tunebook Supplement
* Bards Klezmer Fiddle Tunebook Supplement
* How to Play Violin
* How to Play Fiddle
# BarCamp - How to Run Your Own/Planning

BarCamp tends to attract a lot of people at the start, but after a while people will flake off leaving you with a core team. This is normal. There is a funnel effect to a barcamp planning. By the middle of the planning stage you will be down to a small core team. And by the time of the BarCamp, the team will be bigger with lots of volunteers.
The amount of time you take to plan a BarCamp can vary greatly, depending on the scope and scale of what you want to achieve. The vast majority of time spent organising a BarCamp is put into finding and securing sponsors. Which essentially means that the cheaper your event, the less time you need to plan. I have organised a £3000 BarCamp in 4 months, and my last BarCamp was £5000 and was done in 7 months. That being said, I never really stop planning for the next BarCamp. These timescales indicate how long before the event I start approaching sponsors, whereas in reality, I started scouting the venue for BarCamp Manchester 7 in August, one month before BarCamp Manchester 6 had even begun.
As a BarCamp organiser, it's important to realise just how much of your time is taken up by the event. Even when you are not officially sitting down to work on planning, every building you walk in to you will consider its potential as a BarCamp venue, every shop you enter could be selling potential swag, and every person you meet is a potential sponsor or attendee. When you organise a BarCamp, it can take over your entire life, and this is something you should be prepared for.
# BarCamp - How to Run Your Own/Telling people about it

* Firstly, list your BarCamp at barcamp.org
* If you use Twitter and Facebook, promote it on there.
* Set up a Twitter account for your event (see, for example, @barcamplondon)
* Be sure to promote BarCamp to a wide variety of people: if there are geek communities in your city, approach those. Ask them if they can promote it to their community, and to ask any companies involved in that community if they are interested in sponsoring.
** Language or technology communities might include something like a Python user group or a hardware hacker group.
* Ask other BarCamp organisers if they could promote the event: many will retweet your announcement, blog about it and so on.
* Try and reach out to under-represented communities: some cities have a group for "girl geeks", women in technology etc. Some BarCamps have given a handful of tickets to such communities to hand out at events, although some find this practice slightly controversial.

## Register interest

If you are planning an event but are not ready to start giving out tickets, make a form to just register interest: that way you can get people to just add their e-mail address, and they will get a message when there is a venue and date with instructions on how and when to register for tickets.

## After you've given out tickets

Once people have registered, you need to work out how to keep them engaged. Sending people reminder e-mails is one good way. For BarCampLondon8, the organisers sent out numerous reminder e-mails, and all attendees had to confirm their attendance a week before the event by clicking a link in an e-mail. Using this kind of approach, the organisers reduced the number of people not turning up quite dramatically.
# BarCamp - How to Run Your Own/Schedule and the wall

* Even if you have many rooms as we had, limit the tracks to 4 rooms so the attendance does not suffer.
* Make sure you have at least 8 rooms for the event so sessions will be smaller and more discussion (many to many conversations) take place as opposed to one to many lectures. 4 rooms is not enough.
* Make sure there is plenty of gathering room in front of your wall, people will want to gather round.
* Don't put the wall in one of the session rooms, People will want to look at it mid-session sometimes.

## The Event Slots

* There are different slot sizes you can do, 25 minute slots seems to be about right
* Ensure you give at least a 5 minute break in between sessions

## The Wall

* 5x3 index cards on a whiteboard or physical wall works best
* We used masking tape to form an actual grid
* Put breaks and lunch in as session sized slots - and put cards in that say Lunch or Break
** Don't just write on the tape in between 2 sessions "lunch" people won't see it
* Post it notes tend to fall off in my experience, I prefer index cards with blutack or magnetic whiteboard pins
# BarCamp - How to Run Your Own/Special surprises

It's always good to have something special on the barcamp, here's some of the thing people have done in the past to make their barcamps that little more extra special.
* Games
** Werewolf/Mafia - Theres a rich tradition of introducing people to Werewolf in BarCamps in the UK
** Card and board games are also a good thing to play.
* Midnight surprise
** Popcorn, Pancakes and a Chocolate Fountain at BarCampLondon3
** Krispy Kreme donuts at BarCampLondon6
* Massive video game
** Rock band and Wii sports on a massive screen at barcampmanchester2
# BarCamp - How to Run Your Own/The rules of BarCamp
## The Rules of BarCamp

These are the official rules, they are treated less like rules and more like strong pointers. Try and stay close to them but there's no need to stick to the letter.
COMMUNITY AND INFORMATION
BarCamp is an ad-hoc unconference born from the desire for people to share and learn in an open environment. It is an intense event with discussions, demos and interaction from attendees. Anyone with something to contribute or with the desire to learn is welcome and invited to join. When you come, be prepared to share with barcampers. When you leave, be prepared to share it with the world.
NO SPECTATORS, ONLY PARTICIPANTS
Attendees must give a demo, a session, or help with one, or otherwise volunteer / contribute in some way to support the event. All presentations are scheduled the day they happen. Prepare in advance, but come early to get a slot on the wall. The people present at the event will select the demos or presentations they want to see. Presenters are responsible for making sure that notes/slides/audio/video of their presentations are published on the web for the benefit of all and those who can’t be present.
The Rules of BarCamp
* 1st Rule: You do talk about BarCamp.
* 2nd Rule: You do blog about BarCamp.
* 3rd Rule: If you want to present, you must write your topic and name in a presentation slot.
* 4th Rule: Only three word intros.
* 5th Rule: As many presentations at a time as facilities allow for.
* 6th Rule: No pre-scheduled presentations, no tourists.
* 7th Rule: Presentations will go on as long as they have to or until they run into another presentation slot.
* 8th Rule: If this is your first time at BarCamp, you HAVE to present. (Ok, you don't really HAVE to, but try to find someone to present with, or at least ask questions and be an interactive participant.)
by Tantek Çelik as parodied from The Rules of Fight Club.
Additional guidelines
* Presentations promoting specific commercial products or companies are discouraged. Hold a DemoCamp session/slot for folks to demonstrate specific commercial products etc. rather than take up whole slots with company pitches.
# BarCamp - How to Run Your Own/Venues

* When calculating the cost, consider the following: Additional security, Additional air conditioning and electrical cost. Additional janitorial costs.
* If your office is carpeted, plan on steam cleaning the carpet after the event.
* Plan not to have messy foods such as jelly.
* Work early to make sure that the vendors and caterers meet the insurance requirements for your building (if any).
* Even if you have many rooms (as we had), limit the tracks to between 4 to 8 rooms so the attendance does not suffer.
* Make sure you have at least 8 rooms for the event so sessions will be smaller and more discussion (many to many conversations) take place as opposed to one to many lectures. 4 rooms is not enough.
* Make sure there is enough toilets to cater for the amount of people attending. I would say you want at the very least 2 toilets for 50 people.
* Its worth having a room which is spare to put up the schedule and have as a reception space for people who are not attending the sessions can chill in without upsetting session goers
* Try and pick a venue with either lift access or on one floor for wheelchair barcampers
* Pick venues which you can rope off, to allow barcampers freedom to move and get comfortable within the venue. Nothing worse than people wandering through the barcamp who are not involved
* Venues which are purpose built like offices are ideal but barcamps have been done in many places such as garages, barns, marquees, student unions, etc.
* Outdoor space is great for parties, adhoc sessions and for people to smoke, but bear in mind the weather don't rely on them.
* Think about parking space or how you would get to and from the venue on public transport. Being near a train station is a massive plus for those not local to the area
* Ask yourself if the venue is close to shops and if those shops will be open during the barcamp. You might be able to strike a deal with them for sponsorship
# Cabinet Vision: The Last Mile/Machining Operations
## Miters:

Miters can be placed on edges of parts in one of four ways: By using the shape editor, the object tree, the CAM editor, and by applying operations via that "Reports" tab for the part.
* Shape editor: In the shape editor, click on the edge you want mitered and enter a miter angle for the edge into the bottom input in the left sidebar. This technique is not accessible to UCSs.
* Object Tree: In the Object Tree, you can enter a MITR | MITL | MITB | MITT parameter to the part directly in order to place a miter on the right, left, bottom, or top edge, respectively. This technique is accessible to UCSs.
* CAM Editor: The most reliable means of applying a miter to a part edge is to apply a Line operation in the CAM Editor manually, and assign it to the appropriate v-cutter tool. However, this is only true when the operation is applied to the face of the part that is perpendicular to the z axis of the router. When attempting to apply Line operations manually to edges and then changing the AY parameter in the object tree so as to orient the operation towards the axis of the spindle, CV stops recognizing the operation. Applying a Route operation with a v-cutter tool via UCS is also not very reliable, but assigning a LINE operation as opposed to a route via UCS is functional.
* Apply Operation in Reports: This technique is similar to the CAM editor, except that you can't choose a "Line" operation. Instead, you choose a "Route", and set the width to zero. It seems to have the same advantages and pitfalls of the CAM editor.
When a MIT* Parameter conflicts with the setting of a miter angle set in the Shape Editor, the MIT* Parameter takes precedence over the setting in the Part's Shape.
# Cabinet Vision: The Last Mile/Report Center in Detail

Here is some starter material for now:
1. The report center works, by default, with the Report.mdb. To get information from other sources (CxMaterial, Door.ddb, any .cvc file, etc.) it has to be imported in. Essentially it is importing other database information to work with.
2. A Link is like an import, but instead of directly bringing in data from another database, you configure a view of data using SQL that you can use like any of the other tables in the report.mdb. These are created after Imports.
3. If there is a VBScript on the report, it runs after the previous two are created.
4. Reports have the option "Estimate Materials" in their properties. If this option is checked, it creates the sheet estimate, which is a rudimentary optimization of parts for a sheet count. This happens after the previous three.
5. Reports also have an option for Part Graphics. This option is directly below Estimate Materials in the Report Properties. If this is set to True, then it creates graphics for the parts. This happens after the previous four.
6. After all of this, the actual report is run for you to view. It takes the information from the tables in Report Properties and formats it per the design placed in the Design Report section.
# Cabinet Vision: The Last Mile/Assembly Methods
### Channel Locks

After installing the Lockdowel package, I discovered a significant slowdown because of the sheer number of geometries in their Channelock model. Replace the model with a low-poly variant and the whole system should speed up significantly.
# Cabinet Vision: The Last Mile/General Strategy and Best Practices

There is an order of precedence you should consider when thinking about how to add a new feature to your CV install: First, try the Assembly Method Wizard. Next, try Object Intelligence. Next, look at adding your own Part definitions and assigning them to your own Materials in the Material Schedules. If you're still not there, expand your Catalog with custom configured cabinets that are made smarter with Object Intelligence, maybe also with custom Parts and Materials; If you need even more power, doctor up some Library Parts with parameterized Operations, and use UCSs only to bring them in with the LibPart function. Then, as an absolute last resort, use UCSs to implement things from whole cloth.
You might be very surprised at what you can accomplish with a combination of Object Intelligence and Library Parts. For example, let's say you want a particular part or machining to exist under certain conditions. Before you immediately run off to the UCSs, consider that you can manually add the part or operation, then go into the Object Tree and set its Qty parameter to an Object Intelligence formula that evaluates to 1 when you want the part or operation, and 0 when you don't want it (which might be 99 percent of the time). When you attempt to create things (especially Operations) in UCSs, you enter an entire nightmare world of things that can and do go wrong, and sometimes even cause your system to become unstable and crash.
# Cabinet Vision: The Last Mile/High-Level Strategy

Navigation: Home

## Introduction

It is very important to make wise decisions early in the process of setting up Cabinet Vision. As you add new functionality, and as your shop begins to depend on Cabinet Vision running without disruption, it becomes hard to fix problems baked into the foundation of your CV buildout. The first order of business is configuring how Cabinet Vision represents the 3-dimensional models entered into it.

### General Strategy and Best Practices

The four essential areas of three-dimensional modelling in Cabinet Vision that need configuration are:
* Best Practices for Catalogs
* Best Practices for Assembly Methods
* Best Practices for Object Intelligence
* Best Practices for User-Created Standards
This listing also represents the order of precedence for these strategies, and the increasing difficulty and level of expertise required to implement them well. This means that you should do your very best to set up each area of configuration in sequence, looking to the next one only when it is impossible to achieve the intended result in the current one. You might be surprised at how much you can achieve with object intelligence, for example. Above all, don't make the rookie mistake of immediately looking to UCSs as the solution to all problems. They are powerful and flexible, but that's a double-edged sword. When writing a UCS you need to be careful what you ask for, because once set up, they have a tendency of interfering in situations where you would rather that they not. If you habitually use UCSs to do things that could be done in Catalogs, Assembly Methods, or Object Intelligence, what you'll eventually end up with is an unmanageable mess.
# Cabinet Vision: The Last Mile/Report Center

Here is some starter material:
1. The report center works, by default, with the Report.mdb. To get information from other sources (CxMaterial, Door.ddb, any .cvc file, etc.) it has to be imported in. Essentially it is importing other database information to work with.
2. A Link is like an import, but instead of directly bringing in data from another database, you configure a view of data using SQL that you can use like any of the other tables in the report.mdb. These are created after Imports.
3. If there is a VBScript on the report, it runs after the previous two are created.
4. Reports have the option "Estimate Materials" in their properties. If this option is checked, it creates the sheet estimate, which is a rudimentary optimization of parts for a sheet count. This happens after the previous three.
5. Reports also have an option for Part Graphics. This option is directly below Estimate Materials in the Report Properties. If this is set to True, then it creates graphics for the parts. This happens after the previous four.
6. After all of this, the actual report is run for you to view. It takes the information from the tables in Report Properties and formats it per the design placed in the Design Report section.
# Cabinet Vision: The Last Mile/High-Level Strategy/Best Practices for User-Created Standards
### What could slow your UCS down

There's some common tools provided by Cabinet Vision that are more for use in distributable environments than for people running a version of the software that's capable of editing UCS code. Chief among these is the PUBLIC variable. This will cause CV to do a call back to the variable every time it's used, which will increase runtime on the UCS. Considering it's just for convenience or for distributing a UCS that you may want to include preferences for to someone without an editor, I recommend avoiding using PUBLIC variables entirely, even to the extent of removing them from Developer supplied UCSs.
# C Shell Scripting/snippets
## String manipulation

How to lower and upper case a string using the tr command.
# C Shell Scripting/syntax
## Comparison with Bourne shell
### Features

* List Variables
    C Shell has it Bourne doesn't.
* Shell Functions
    Bourne has it C Shell doesn't

### Syntax differences

* comments
* assigning variables
* expressions
Bourne has more advanced command substitution syntax for embedding. (Bourne Shell Scripting/Substitution)
vs
# Cabinet Vision: The Last Mile
## Purpose of this Wikibook

Cabinet Vision is an industry-leading CAD/CAM system in support of the cabinet manufacturing industry. The supplied documentation and videos available from the official Cabinet Vision E-Support web site provide an introduction to the system, along with plenty of useful information on what feature of the application performs what action. However, these materials have relatively little to say about strategies, tactics, and best practices for building out a flexible and full-featured CV installation for a manufacturer of highly-customized cabinetry. The Forums on the E-Support site are presently the main (albeit informal) source of advanced knowledge, presented in a conversational format. Although these resources are indispensable, they don't constitute a complete User's Guide. The result is that many CV technicians struggle to achieve more than beginner-level proficiency with Cabinet Vision, and can't decide which one of the many possible approaches to solving some problem will serve them best in the long run. This guide is intended to remedy that. It is intended as a supplement to these other sources of information, but it is not—nor can it be—a replacement for them.

### Intended Audience

Before turning to this guide, you should have watched all or most of the introductory videos on Cabinet Vision and have a good understanding of the various components of the Cabinet Vision user interface. For example, you should know how to use the Assembly Method Wizard and create at least a rudimentary User Created Standard. Perhaps you have your installation of Cabinet Vision set up to generate some rough approximation of your intended build standards, but at this point you don't know the next steps to get it running the way you really want it.
There will also be chapters of this Wikibook intended for advanced users who are pushing the limits of what Cabinet Vision can do.

### Contributions

Nobody owns this Wikibook. It is everyone's to read and edit. There are many Cabinet Vision techs whose expertise has the potential to save days or weeks of frustration for a new (or not-so-new) CV tech. All who have expertise that they would like to share are invited to contribute to this Wikibook. Do it not just for the benefit of others, but also to document useful discoveries for your own future reference. Likewise, there are many "classic" posts people have made on the forums that some of us keep bookmarked because they are so useful. But not everyone has your bookmark collection, so feel free to copy the content of those posts into this Wikibook.

### Table of Contents

* General Strategy and Best Practices
* Catalog Techniques
* Assembly Method Techniques
* Object Intelligence Techniques
* User Created Standards Techniques
* Shaped Cabinets and Parts in Detail
* Machining Operations in Detail
* Report Center in Detail
* Undocumented System Parameters
1. High-Level Strategy
2. Catalogs
3. Assembly Methods
4. Object Intelligence
5. User Created Standards
6. The Details of Machining Operations
7. The Report Center
8. Shaped Cabinets and Parts