Hugh Gene Loebner

  The AISB were sad to learn last week of the passing of philanthropist and inventor Hugh Gene Loebner PhD, who died peacefully in his home in New York at the age of 74.  Hugh was founder and sponsor of The Loebner Prize, an an...


AI Europe 2016

  Partnership between AISB and AI Europe 2016: Next December 5th and 6th in London, AI Europe will bring together the European AI eco-system by gathering new tools and future technologies appearing in professional fields for th...


AISB convention 2017

  In the run up to AISB2017 convention (, I've asked Joanna Bryson, from the organising team, to answer few questions about the convention and what comes with it. Mohammad Majid...


Harold Cohen

Harold Cohen, tireless computer art pioneer dies at 87   Harold Cohen at the Tate (1983) Aaron image in background   Harold Cohen died at 87 in his studio on 27th April 2016 in Encintias California, USA.The first time I hear...


Dancing with Pixies?...

At TEDx Tottenham, London Mark Bishop (the former chair of the Society) demonstrates that if the ongoing EU flagship science project - the 1.6 billion dollar "Human Brain Project” - ultimately succeeds in understanding all as...


Computerised Minds. ...

A video sponsored by the society discusses Searle's Chinese Room Argument (CRA) and the heated debates surrounding it. In this video, which is accessible to the general public and those with interest in AI, Olly's Philosophy Tube ...


Connection Science

All individual members of The Society for the Study of Artificial Intelligence and Simulation of Behaviour have a personal subscription to the Taylor Francis journal Connection Science as part of their membership. How to Acce...



AISB Quarterly Submissions and Suggestions


Click here to go straight to submissions guidelines.

There are several ways that you can contribute to the Quarterly:

  • Send us ideas of general topic areas that you think should be covered and (if possible) the names of people in these areas who could join our Editorial Board. Feel free to volunteer yourself: see the job description below.
  • If there are features or columns that you'd like to see, but that don't fit the existing format, please let the Editor know what you have in mind.
  • If you are aware of particular projects that should be covered, or particular people who would write good articles, please let the Editor know. (We just need a name and affiliation/e-mail address or URL).
  • If you would like to write an article about your own work, please get in touch. If your proposal is accepted, you will be asked to submit according to the deadlines and submissions guidelines below
  • If you would like to write a book review, or plan to submit a conference report, please check out our special guidelines.



The AISBQ is issued in the first week of the quarter (January, April, July, October). Whatever you would like to contribute, the list below explains roughly when we need your input for a particular edition.

For the exact dates, please contact the Editor.

Editorial Board and feature suggestions

Deadline: 16 weeks from issue.

Author/project suggestions

Deadline: 12 weeks from issue.

Article submission deadline

Deadline: 7 weeks in from issue.


Editorial Board Member: Job Description

To join our board, simply check to see that no-one in the Editorial Board is currently covering your topic area, and then contact the Editor. What we will ask you to do is as follows:

  • Every time you go to a conference, send us the details of at least one good paper that you think would interest the general AISB audience.
  • Every time you are asked (once a quarter) send at least one suggestion of an author/group/project who should be covered in the newsletter.
  • As they occur to you (could be never!) send ideas for new features, suggest areas that are not covered sufficiently, submit names of potential Editorial Board members.

NB: You can do the job for as long or as short a period as you like. However, if you fail to submit a suggestion for two quarters in a row you will be taken off the list.


Submissions Guidelines: Checklist

  1. Send both an electronic version and hardcopy to the Editor.
  2. Make sure to keep text and figures in separate files: and figures should never be inside Word documents.
  3. Don't send a LaTeX file unless the codes are stripped out
  4. If you're sending ASCII text, make sure you've used our codes for special characters.
  5. Don't e-mail large (more than 1 or 2Mb) files without checking first.
  6. Make sure your references are in the right style.
  7. Keep formatting to a minimum.
  8. Send colour figures only if a) you think colour is really important and you want them in colour in the electronic version of the Quarterly and b) you have checked that they look OK in black and white!



Your article should be aimed at people within Artificial Intelligence and Simulation of Behavior but who are not  in your particular discipline. Bear in mind that this includes a very disparate collection of people: some will have computer science backgrounds, some electrical and electronic engineering, others cognitive science, psychology or medicine. The article should:

  • Explain the application and context of your work in the wider sense (1-2 paragraphs)
  • Focus on it's position within your general discipline (1-2 paragraphs)
  • Explain the actual project in general terms (2-3 paragraphs)
  • Describe the results and conclude (2-3 paragraphs).

This is based on the ideal 100 word paragraph.

As you see, we don't want much, just about 800 words including figure captions and references. The article should be accompanied by one or two figures that help explain your work, and for which you hold copyright.

You should submit text both electronically (by e-mail) in the format described in the next section, and as either hard copy (by snail-mail to the Editor) or as a .pdf file with fonts included. This way everything can be double-checked. Before sending anything, however, please make sure that your files are in the correct electronic format.



Essentially unformatted text is required: please don't bother to try to make it look pretty (no centered titles,  complicated margins/tabs, justified text etc). It's going to appear in a completely different form, so the main thing is just to get the data across.

If your text file is in any standard wordprocessing (like Word, Wordperfect, Rich Text Format etc.) format, it should be easy to convert. But  please keep things simple by doing the following:

  • If you have to specify a font in the document, use Times 14 pt if you can (or another standard laserwriter font if you can't).
  • Don't put the text and figures in the same file, or show us where to place the figures. Just provide "callouts" (such as "see Figure 1") in the text, and put captions at the end.  With the caption, please include the figure file name as follows:

Figure 1: {bainsfig1.jpeg} Shown is the set-up for the real time camera system...

  • Use real numbers (not Word relative numbering) for the references (and follow the reference guidelines).



Non-standard elements often get lost when they are converted, so give us a text conversion key to avoid embarrassing errors (such as microseconds being turned into milliseconds). This way, we can figure out what you meant if the characters change en route, and we can see if there is a problem with characters going missing.

  • At the top of the document, list any non-standard characters you have used in the text (use the actual character), and then spell them out  surrounded by a single set of curly brackets. For instance:

$ = {dollar sign}

lower-case lambda = {lambda)

upper-case delta = {DELTA}

e-grave = {e grave}

Sorry, by definition real special characters don't show up properly in html. (The dollar sign is only included to show the form required.)

If you cannot supply text in one of the wordprocessing formats listed above (ask if you're not sure whether your format will work), please supply a raw ASCII file. ASCII-users must take care of special characters by encoding them as {DELTA}, etc., throughout the text. In addition, ASCII-users must make sure that super and subscripts are correctly labelled.

  • Use double curly brackets around characters which should be subscript. Eg. TEM{{00}} and LiNbO{{3}}.
  • Use triple curly brackets around characters which should be superscript. Eg. 10{{{-12}}} or {psi}{{{*}}}.

If you are having trouble precisely specifying mathematical symbols, looking at the relevant Unicode charts may help. Just specify which character you need in which table of which chart.

LaTeX users: if you can avoid it, don't use LaTeX. If you absolutely have to, please make sure to strip out all codes except those referring to text features and foreign characters such as those listed above. LaTeX conventions for italic, subscript etc. are OK.



In the text they should be represented as superscript, with the number after any comma or period that happens to appear at the same place. In the listing at the end they should be written as follows:

For a paper:

1. C. C. Wu, J. C. Sturm, R. A. Register and M. E. Thompson, Integrated three-colour organic light-emitting devices,  Appl. Phys. Lett. 69 (21), p 3117, 18 November 1996.

For a book:

1. J. Astola and P. Kuosmanen, Fundamentals of Nonlinear Digital Filtering, CRC Press LLC, Boca Raton, 1997.

Note, in the examples given there are no quote marks anywhere and the commas are italic or emboldened with the text that precedes them. Also, only include the details of the place/date of a conference if you have no proceedings or volume number. Book editors should also be omitted for proceedings (not for ordinary books) where the correct volume information is supplied.



Do not send figures as part of a wordprocessing (especially Word) file: this almost never works well. Send each figure as an separate file, preferably with your name in the filename (such as bainsfig1.tiff). Also, we cannot directly work with figures composed in Word: you will have to convert them, with sufficient resolution, yourself.

Make sure the figures are black and white. If they start as colour, save them as greylevel images so that: (a)  you can see what they look like without colour, and (b) they will be smaller and therefore easier to send.

If you really want colour, provide a b/w figure for the newsletter and put a colour version of the figure on the web. Then, simply include the appropriate URL in the figure caption.

For electronic submissions, EPS format is preferred, although JPEG, PICT, and TIFF files are also usable (documents must be importable to PageMaker). Ask if there is something else you'd like to use. The ideal figure is greylevel with of the order of 400-1000 pixels on a side (but readable at 30% scale), and 200-500k in size. If it's more than 500k, you should ask yourself why!

Thanks for reading the guidelines!