Our research

Our academic staff are at the forefront of global thinking on issues relating to wealth and wellbeing, strong organisations, transformative innovation, and the

Student resources

Information about program and course selection, enrolment, change of program, variation to enrolment, status and other general matters.

Alumni

Our alumni may be found in the world’s leading companies, policy agencies and universities.

Contact us

Find contact details for any general enquiries.

1. Procedural Guidelines for Using the CBE Behavioural Labs

1.1. Recruitment and Management of Participants

Please note that the recruitment and management of participants, as well as payments to them, are the researcher’s responsibility. CBE is in the process of developing a policy with regard to participant pools.

 

1.2. Number of Participants per Session

Please note that due to limited capacity of Multi-Purpose Lab (i.e., 18 computers) and Advanced-Equipment Lab (i.e., 1 computer for experiments involving physiological measures and 2 computers for other experiments), the maximum number of concurrent participants allowed in Multi-Purpose Lab is 18 and Advanced-Equipment Lab is 1 (if physiological measures are involved) otherwise, 2.

 

1.3. Lab Access

a) Upon arrival, the Lab Manager will issue the researcher with a key to the lab. It is the researcher’s responsibility to return the key to the Lab Manger at the end of the session.

b) For every session, time slots of 15 minutes each are allocated before and after the session's actual time. It is the responsibility of the researcher to arrive at the lab early (maximum 15 minutes before the start of your session) to make the necessary preparations and depart within 15 minutes before the end of your session. However, if a researcher requires more time, an explicit request can be made at the time of making a booking request.

 

1.4. In the Lab

a) It is the researcher's responsibility to go through the workplace health and safety related presentation (WHS Presentation) with the participants at the start of every session. The presentation is copied to the desktop of all the labs' laptops. 

b) A profile on a Fileserver can be created on your behalf to store digital data. However, it is the researcher’s responsibility to remove the data at the end of the session.

c) With the exception of cold water, no food or drinks are allowed in the labs.

d) The researcher should inform the participants to be careful when drinking water and to not spill it on equipment.

e) Remember to collect the consent forms (approved by the Ethics Committee) signed by the participants.

f) In case of any problems with the software or hardware, please contact the Lab Manager. Also, if any software or hardware is not working, please inform the Lab Manager so that it can be fixed immediately.

g) Lab computers are not for personal use. The researcher using the lab should convey this to the participants.

h) The researcher must not leave the participants unattended.

i) The lab must be locked if unattended.

 

1.5. After the Session

It is the researcher’s responsibility to remove all material brought into the lab.

 

1.6. Licenses

It is the responsibility of the researcher to ensure that all the licence-related obligations of the software used are met. For example, if Ztree experiment software is used, the researcher must cite the following article in their paper: Urs Fischbacher (2007): z-Tree: Zurich Toolbox for Ready-made Economic Experiments, Experimental Economics 10(2), 171-178. E.g., write "The experiment was programmed and conducted with the software z-Tree (Fischbacher 2007)

 

1.7. Privacy Policy

a) All paper-based data collected by the researcher (e.g., personally-identifying data, forms etc.) is the responsibility of the researcher conducting the study and should be removed from the lab after each session.

b) All data privacy and security rules of The Australian National University must be followed and no private data should be left in the lab.

 

1.8. Booking, Cancelling or Changing Time for a Lab Session

a) Bookings must be made at least 5 business days in advance of the first session.

b) Any researcher who wants to cancel (or change the time for) a session must email the Lab Manager at least 5 business days ahead of the original booking. Any cancelation or rescheduling requests with less than 5 days’ notice will be counted against the researcher’s quota (please see 1.9 for more details) on the original and the new bookings.

c) No lab reservations are complete until a confirmation email has been received from the Lab Manager.

d) Please note no lab can be reserved for one researcher for more than 24 hours within a one-week period.

 

1.9. Using CBE Behavioural Labs outside of Office Hours

Any researcher who needs to use CBE Behavioural Labs outside of office hours should contact the Lab Manager at least 3 weeks in advance of the first outsdie-of-office-hours session. The Lab Manager will then forward the "Terms and Conditions of Using CBE Behavioural Labs outside of Officer Hours" to the researcher and make other arrangements such as obtaining outside-of-office-hours access on the visitor pass. 

1.10. Allotted Quota

a) Academic staff and Post-Docs have an allotted number of hours per teaching semester that they can use to reserve time (combined for Multi-Purpose Lab and Advanced-Equipment Lab).

-  Academic staff = 50 hours

-  Post-Docs = 30 hours

-  PhDs and MPhil = 20 hours

b) The above rule applies when the labs are at full capacity.

 

1.11.   Miscellaneous

a) Please note printed posters are not allowed to be posted on the doors or walls.

b) The Multi-Purpose Lab can be used for teaching if it is free and other normal labs are not available.

c) Participant pools are organized by relevant schools until further notice.

d) Academic staff, post-docs and research students from CBE are given priority over other colleges but noting the Research School of Computer Science, ANU allocation.

e) No electrical devices such as laptops or computers are allowed in the labs which are not issued with safety tags by ANU

 

2. Requesting for New Software

Please note that requests for new software will be handled on a case by case basis. A researcher may request the labs to pay for a new software (Scenario 1), offer to pay for a new software himself/herself (Scenario 2) or install software available free of cost (Scenario 3). 

 

2.1. Scenario 1: Requesting the Labs to Purchase New Software

a) The researcher emails the Lab Manager about the software.

b) The Lab Manager checks if there are any compatibility issues.

c) If there are no issues, the researcher then makes a case about how other researchers and the BLabs would benefit from the software.

d) The case then will be forwarded to the Hub Director for approval. If approved, the process of purchasing, deploying and testing of the software will start.

e) Please note that a time window of 12 weeks should be spared for fee-based software to allow time for quoting, purchase order, and in some cases communicating with Information Technology Services (ITS) ANU.

 

2.2. Scenario 2: A researcher would like to Pay for the Software

a) The researcher emails the Lab Manager about the software.

b) The Lab Manager checks if there are any compatibility issues.

c) If there are no issues, the request will be forwarded to the Hub Director for approval. If approved the purchasing, deploying and testing of the software will start.

d)  Please note that a time window of 12 weeks should be spared for fee-based software to allow time for quoting, purchase order, and in some cases communicating with Information Technology Services (ITS) ANU.

2.3. Scenario 3: Requesting for Free Software

a) The researcher emails the Lab Manager about the software.

b) The Lab Manager checks if there are any compatibility issues.

c) If there are no issues, the Lab Manager forwards the request to the Hub Director for approval. If approved, the software installation and testing will start.

d) Please note that a time window of 6 weeks should be spared for free software to allow for software deployment, testing by IT and for the Lab Manager to develop familiarity with the software.

Updated:   23 November 2017 / Responsible Officer:  Dean, Business & Economics / Page Contact:  College Web Team