OpenLLM-France/wikimedia huggingface dataset:
# Java Programming/Annotations/Meta-Annotations

* Navigate Javadoc & Annotations topic: ( v • d • e )
* Javadoc
* Introduction to Annotation
* Creating custom annotations
* Meta-annotations
* Helping the compiler
There are five annotation types in the java.lang.annotation package called meta-annotations. These annotation types are used to annotate other annotation types.

## Documented

If a member is annotated with a type itself marked as @Documented, then that member will be documented as annotating that type.
* Code listing 1.1: Use of @Documented
* @interface Secret { }
* @Documented
* @interface NotSecret { }
* @Secret
* @NotSecret
* public class Example {
In the documentation for the Example class, such as the JavaDoc, Example will be shown as annotated with @NotSecret, but not @Secret.

## Inherited

Exactly as the name sounds, an @Inherited annotation type is inherited by subclasses of an annotated type.
* Code listing 1.2: Use of @Inherited
* @Inherited
* @interface ForEveryone { }
* @interface JustForMe { }
* @ForEveryone
* @JustForMe
* class Superclass { }
* class Subclass extends Superclass { }
In this example, Superclass has been explicitly annotated with both @ForEveryone and @JustForMe. Subclass hasn't been explicitly marked with either one; however, it inherits @ForEveryone because the latter is annotated with @Inherited. @JustForMe isn't annotated, so it isn't inherited by Subclass.

## Repeatable

A @Repeatable annotation type is repeatable - i.e. can be specified multiple times on the same class. This meta-annotation was added in Java 8.

## Retention

Different annotation types have different purposes. Some are intended for use with the compiler; others are meant to be reflected dynamically at runtime. There's no reason for a compiler annotation to be available at runtime, so the @Retention meta-annotation specifies how long an annotation type should be retained. The value attribute is one of the java.lang.annotation.RetentionPolicy enum constants. The possible values, in order from shortest to longest retention, are as follows:

### RetentionPolicy.SOURCE

    The annotation will not be included in the class file. This is useful for annotations which are intended for the compiler only.

### RetentionPolicy.CLASS

    The annotation will be included in the class file, but cannot be read reflectively.

### RetentionPolicy.RUNTIME

    The annotation can be reflected at runtime.
If no @Retention policy is specified, it defaults to RetentionPolicy.CLASS.

## Target

The @Target meta-annotation determines what may be marked by the annotation. The value attribute is one or more of the java.lang.annotation.ElementType enum constants. Those constants are ElementType.ANNOTATION_TYPE, CONSTRUCTOR, FIELD, LOCAL_VARIABLE, METHOD, PACKAGE, PARAMETER, and TYPE.
If @Target is not specified, the annotation may be used on any program element.
# Java Programming/Applets/Event Listeners

Navigate User Interface topic:( v • d • e )
Basic I/O
Streams
Event handling
JavaBeans
Canvas
Graphics
Drawing basic shapes
Drawing complex shapes
Drawing text
Understanding gradients
Applets
Overview
User Interface
Event Listeners
Graphics and Media :
An Event Listener, once set to an applet object, waits for some action to be performed on it, be it mouse click, mouse hover, pressing of keys, click of button, etc. The class you are using (e.g. JButton, etc.) reports the activity to a class set by the class using it. That method then decides on how to react because of that action, usually with a series of if statements to determine which action it was performed on. source.getSource will return the name of the object that the event was performed on, while the source is the object passed to the function when the action is performed. Every single time the action is performed, it calls the method.

## ActionListener

ActionListener is an interface that could be implemented in order to determine how a certain event should be handled. When implementing an interface, all methods in that interface should be implemented, ActionListener interface has one method to implement named actionPerformed.
The code listing 9.6 shows how to implement ActionListener:
* Code listing 9.6: EventApplet.java
* import java.applet.Applet;
* import java.awt.Button;
* import java.awt.Container;
* import java.awt.Dialog;
* import java.awt.FlowLayout;
* import java.awt.Frame;
* import java.awt.Label;
* import java.awt.event.ActionEvent;
* import java.awt.event.ActionListener;
* public class EventApplet extends Applet {
* * Init.
* public void init {
* Button clickMeButton = new Button("Click me");
* final Applet eventApplet = this;
* ActionListener specificClassToPerformButtonAction = new ActionListener {
* public void actionPerformed(ActionEvent event) {
* Dialog dialog = new Dialog(getParentFrame(eventApplet), false);
* dialog.setLayout(new FlowLayout);
* dialog.add(new Label("Hi!!!"));
* dialog.pack;
* dialog.setLocation(100, 100);
* dialog.setVisible(true);
* private Frame getParentFrame(Container container) {
* if (container == null) {
* return null;
* } else if (container instanceof Frame) {
* return (Frame) container;
* } else {
* return getParentFrame(container.getParent);
* clickMeButton.addActionListener(specificClassToPerformButtonAction);
* add(clickMeButton);
When you compile and run the above code, the message "Hi!!!" will appear when you click on the button.

## MouseListener

Applet mouse listener does not differ from the AWT mouse listener in general. When the mouse is in the applet area, the listener receives notifications about the mouse clicks and drags (if MouseListener is registered) and mouse movements (if MouseMotionListener is registered). As applets are often small, it is a common practice to let applet itself to implement the mouse listeners.
# Java Programming/Annotations/Compiler and Annotations

* Navigate Javadoc & Annotations topic: ( v • d • e )
* Javadoc
* Introduction to Annotation
* Creating custom annotations
* Meta-annotations
* Helping the compiler
Annotations can be used by the compiler to carry out certain directives. Much that you'd love programming in Java, you probably would have been fussed about compiler warnings. Compiler warnings are not necessarily errors but are warnings that tell you the code might malfunction because of some reason.

### Taming the compiler

You can issue directive to the compiler in the shape of three pre-defined annotation to tell it what sort of pre-processing a certain bit of code requires. The three annotations are:
* @Deprecated
* @Override
* @SuppressWarnings(..)
@Deprecated is used to flag that a method or class should no longer be used, normally because a better alternative exists. Compilers and IDEs typically raise a warning if deprecated code is invoked from non deprecated code.
@Override flags that a method overrides a method in a superclass. If there is no overridden method, a compile error should occur.
@SuppressWarnings(..) SuppressWarnings tells the compiler not to report on some, or all, types of warnings. It can be applied to a type, a method or a variable.

## External links

* Advanced usage of the @SuppressWarnings(..) annotation
# Java Programming/Applets

Navigate User Interface topic:( v • d • e )
Basic I/O
Streams
Event handling
JavaBeans
Canvas
Graphics
Drawing basic shapes
Drawing complex shapes
Drawing text
Understanding gradients
Applets
Overview
User Interface
Event Listeners
Graphics and Media :
* Overview
* User Interface
* Event Listeners
* Graphics and Media
# Java Programming/Applets/Graphics and Media

Navigate User Interface topic:( v • d • e )
Basic I/O
Streams
Event handling
JavaBeans
Canvas
Graphics
Drawing basic shapes
Drawing complex shapes
Drawing text
Understanding gradients
Applets
Overview
User Interface
Event Listeners
Graphics and Media :

### Painting

By overriding the update(Graphics g) and paint(Graphics g) methods of an Applet (or one of its subcomponents), you can have fairly direct control over the rendering of an Applet. The Graphics object provides various primitives for working for two-dimensional graphics.
# Java Programming/Annotations/Custom Annotations

* Navigate Javadoc & Annotations topic: ( v • d • e )
* Javadoc
* Introduction to Annotation
* Creating custom annotations
* Meta-annotations
* Helping the compiler
Annotations can be viewed as a source of defining meta-data for a piece of code in Java. The annotation @CodeDescription used in the following sections does not come as a part of the Java API.

## Annotation Type Declaration

Before you can use an annotation with classes, theirs members and statements or expressions, you need to define an annotation type. Following is the syntax on how to define a type for the mentioned annotation.
* Code listing 1.1: Annotation type declaration
* @interface CodeDescription
* String author;
* String version;
That's it! Our first ever annotation has been defined. Now, we can use it with any of our classes. An annotation definition if you look closely resembles the definition of a normal interface, except that the interface keyword is preceded by the @ character. Some refer to this syntactical declaration as the annotation type declaration due to the fact that @ is 'AT' or 'Annotation Type' for that very instance.

## Annotation Element Declarations

What look like methods in the body of the annotation definition are called annotation element declarations. These are the named entities that we used with the annotation body in the example in the previous section. However, for the sake of clarity, code below also represents the calling of the following annotation:
* Code listing 1.2: Calling of annotation
* public class MyMethod
* @CodeDescription
* author = "Unknown",
* version = "1.0.0.1"
* public void doSomething

## Using a default value

Now, for instance, you want the annotation to know that if no value for the version element is present, then it should use a default value. Declaring a default value would be done the following way.
* Code listing 1.3: Using default values.
* @interface CodeDescription
* String author;
* String version default "1.0.0.1";
So, now if you use the same code again, you can ignore the version element because you know that the value is to be provided by default.
* Code listing 1.4: Pre-defined value.
* public class MyMethod
* @CodeDescription(author = "Sysop")
* public void doSomething
# Java Programming/Annotations/Introduction

* Navigate Javadoc & Annotations topic: ( v • d • e )
* Javadoc
* Introduction to Annotation
* Creating custom annotations
* Meta-annotations
* Helping the compiler

## Introduction

In Java, an annotation is a language construct (introduced in J2SE 1.5) that provides a mechanism for including metadata directly in the source code.
Annotations can provide metadata for Java classes, attributes, and methods. Syntactically, annotations can be viewed as a special kind of modifier and can be used anywhere that other modifiers (such as public, static, or final) can be used.
One of the main forces of adding this feature to Java was the wide spread use of XML descriptors to add additional information, metadata, for Java classes. Frameworks like EJB, JSF, Spring, Hibernate were heavily using external XML descriptors. The problem of those external descriptors was that those files are out of reach of the Java compiler and for that reason compiler type checking could not be used. A small spelling mistake bug in a huge XML descriptor file is hard to locate and fix. On the other hand the Java annotations use the Java compiler type checking features so spelling mistakes in annotation names will be caught by the Java compiler.
In summary, annotations can be...
* used as a source of information for the compiler;
* made available for compile-time or deployment-time processing;
* examined at runtime.

## External links

* The Java™ Tutorial on Annotations
# History of wireless telegraphy and broadcasting in Australia/Topical/Biographies/Sydney Victor Colville
### Sydney Victor Colville

Sydney Victor Colville was an early wireless experimenter from 1912 (callsign: XQF), prominent amateur club administrator (Queensland Wireless Institute), amateur telephony experimenter (1920, Qld), radio business proprietor (Colville Moore Wireless Supplies). His station callsigns were 4FA (Brisbane) and 2FA (Sydney). A summary biography has not yet been prepared however the following resources have been assembled in preparation:
* Transcriptions and Notes - Sydney Victor Colville - More than 50 transcriptions and notes
* Photos, QSL cards and other graphics - Sydney Victor Colville - Nothing uploaded as yet
# History of wireless telegraphy and broadcasting in Australia/Topical/Biographies/Sydney Moreton Newman/Research

To date all research has been very largely limited to NLA's Trove, and further to Trove, Newspapers & Gazettes
In the National Library of Australia's Trove website, XXX articles (Newspapers & Gazettes) as at 6 April 2021 have been tagged as "XPZ-3MC - Sydney Moreton Newman" (search publictag:XPZ-3MC - Sydney Moreton Newman)
The main searches used to identify articles for tagging are as follows:
* With phrase "Sydney Moreton Newman" initially about 10 hits, now all tagged articles are hits
* With phrase "S. M. Newman", (about 20 hits)
* With phrase "Sydney M. Newman", (about 20 hits)
* With words "Newman" and "Wireless" (about 20 hits)
Key articles relating to Watkins and wireless, also Watkins' family history, have been identified for text correcting and inclusion in Transcriptions and Notes - Sydney Moreton Newman. Articles transcribed for Notes are tagged: "!Wikibooks Newman" (10+ articles). Articles reviewed and considered either duplicates of other articles or not of sufficient importance for inclusion are tagged: "!Wikibooks Newman Not" (10+ articles).
# History of wireless telegraphy and broadcasting in Australia/Topical/Biographies/Thomas Edward Self
### Thomas Edward Self

A comprehensive biography of Thomas Edward Self has not yet been prepared, however the following resources have been assembled in preparation:
* Research - Thomas Edward Self - Summary of research to date
* Transcriptions and Notes - Thomas Edward Self - More than 50 transcriptions
* Photos, QSL cards and other graphics - Thomas Edward Self - Nothing uploaded as yet
* Incubator of Wikipedia Article on Thomas Edward Self - Coming real soon now!
IN RESEARCHING THOMAS EDWARD SELF, THE TELEGRAPHY ENGINEER AND WIRELESS EXPERIMENTER, BE AWARE THAT HIS FATHER WAS OF THE SAME NAME AND ANOTHER UNRELATED THOMAS EDWARD SELF LIVED IN HOBART THROUGH THE SAME PERIOD
Pending further progress on the foregoing, the following brief obituary in the Hobart Critic of 29 October 1915 for Thomas Edward Self touches briefly on his contribution to the development of communications in Tasmania in the latter years of the 1800s and the early 1900s
   Commentator. . . . The death of Mr. Thomas E. Self takes one’s memory back to the days of long ago, when the then generation travelled by coach, and went dead slow in the avocations of life. Tom came from good old English stock, and was one of those characters who from youth to manhood gently rolled through the world without any undue fuss, and as a rule always reached the goal he made for. He had a pleasant personality and was a bright, good-hearted fellow, and a warm friend. In his early days he was a prominent member of the Galatea Cricket Club, which made a name for itself in the seventies. Tom was a long-stop. Most balls he missed with his hands he fielded with his legs. This procedure, which can hardly be called legitimate, kept down runs, and earnt for Tom the title of the "Man with the iron legs." Being of a mechanical bent, he joined the constructive and mechanical branch of the telegraph department, and reached a highly responsible position. He was one of those who assisted to lay the submarine cable across the river from Government House Point to Lindisfarne in 1885, and when he was transferred to the Commonwealth department he took up an important appointment in the construction department of telegraphic and telephonic extension. Of late years the subject of this brief notice has been suffering from bodily ills, and he was compelled to relinquish work. When one last met him, he was cheerful, and when one alluded to his trouble, he philosophically replied: "There are heaps of worse things in the world." The deceased was an all-round lover of sport, and in his younger days was actively engaged in aquatic pursuits.
* ↑ "Commentator.". Critic (Tasmania, Australia) XI, (539): p. 2. 29 October 1915. http://nla.gov.au/nla.news-article169019786. Retrieved 3 February 2021.
# History of wireless telegraphy and broadcasting in Australia/Topical/Biographies/Robert Kelvin Allen

Robert Kelvin Allen was a prominent amateur operator and amateur broadcaster in the late 1930s. He was educated at Scots College at Warwick and was appointed to the Queensland state public service with the Treasury Department. His station callsign was 4PR (4=Queensland, P=?, R=?) and he operated from Brisbane and Toowoomba, Queensland. He joined the RAAF in 1940, shortly after the commencement of the Second World War, excelled in the examinations and qualified as a pilot. In January 1942, he sadly passed in an aircraft accident in the the Netherlands East Indies (now Indonesia). "Greater love hath no man than this"
A summary biography has not yet been prepared however the following resources have been assembled in preparation:
* Transcriptions and Notes - Robert Kelvin Allen - More than 20 transcriptions and notes
* Photos, QSL cards and other graphics - Robert Kelvin Allen - Nothing uploaded as yet
A brief biography of former students of Scots College, Warwick, who made the supreme sacrifice (including 4PR) was published in 2007.
Each year, the Wireless Institute of Australia conducts a Remembrance Day contest to celebrate the lives of Australian amateur operators killed in action in the Second World War. As at 2020, Michael Charteris (VK4QS) is working on a book of biographies to record those who made the ultimate sacrifice and it is expected to be published by the Wireless Institute of Australia in 2021.

## References

* ↑ Telfer, John Robert; Scots College (Warwick, Qld.) (2007), Profiles of courage : a collection of short stories of the young men of The Scots College Warwick, Queensland who made the supreme sacrifice in World War II 1939-1945, The SCOTS PGC College, ISBN 978-0-646-49019-9
# History of wireless telegraphy and broadcasting in Australia/Topical/Biographies/Sydney Moreton Newman
## Sydney Moreton Newman

* Sydney Moreton Newman | Newman, Sydney Moreton "Syd" - 1898(NSW)-1998(NSW)99yo - Licences: XPZ Melbourne (Canterbury, 1913-1914); 3MC Melbourne (Canterbury, 1923-1927) - Qualifications: cc; CPRT 655, 1921; 1COCP 90, 1930 - early wireless experimenter; amateur operator; amateur broadcaster - Electoral Rolls: radio engineer (Turramurra, 1930-1958); retired (Wahroonga, 1963-1980) - TroveTag: "XPZ-3MC - Sydney Moreton Newman" (68 tags) - Links: EA

### Resources

A comprehensive biography of Sydney Moreton Newman has not yet been prepared for this Wikibook, however the following resources have been assembled in preparation:
* Research - Sydney Moreton Newman - Summary of research to date
* Transcriptions and Notes - Sydney Moreton Newman - More than 70 transcriptions and notes
* Photos, QSL cards and other graphics - Sydney Moreton Newman - Nothing uploaded as yet, but several photos identified
* Incubator of Wikipedia Article on Sydney Moreton Newman - Coming real soon now!

### Internet Material

Neville Williams authored a wonderful 6 page biography of Newman in the January 1991 edition of Electronics Australia Sydney Newman. This biography is quite comprehensive and needs only electronic citations for completeness.
# MCEM Part A Study Guide/Preparation/Books
## Study Guides

* Revision Notes for MCEM Part A (Oxford Specialty Training: Revision Texts)
* Oxford Handbook of Emergency Medicine.
* BNF (latest edition) for pharmacology.
* Lasts anatomy / Snell's clinical anatomy.
* Ganong's physiology / Physiology at a glance
* MRCP revision notes by Philippa Esterbook (for immunology and statistics)
* Practise papers for MCEM part A by Jaydeep Chitnis.

## Sample MCQs

Get Through MCEM Part A MCQS: Part A
Practice Papers for MCEM Part A

## Subject Specific References

The MCEM syllabus itself recommends "Physiology at a Glance" as the level of detail required.
The MCEM syllabus references the BNF extensively in the Pharmacology Section.
# MINC/EZMINC/DistortionCorrection
## Geometric distortion correction Tools

TODO
# MCEM Part A Study Guide/Preparation

The Membership of the College of Emergency Medicine Part A Exam obviously requires a considerable amount of preparation.
While this Wikibook is designed to be a comprehensive study guide, people have many different methods of learning and it would be amiss to ignore the other excellent resources available. We will also aim to keep a relatively brief, objective guide to other helpful resources such as books and courses.
# MINC/FAQ
### MINC Frequently asked questions will be here

* Where to ask for help
** Questions on using MINC: MINC-users mailing list : MINC-usersbic.mni.mcgill.ca http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-users
** Questions on MINC development: MINC-development mailing list : MINC-developmentbic.mni.mcgill.ca http://www.bic.mni.mcgill.ca/mailman/listinfo/minc-development
# MINC

Introduction - The How, What and Where of MINC
History - The Who and When of MINC
MincWorld - Who uses and develops software based on MINC
Installation - Tutorials for installing the MINC tools and associated software
FAQ - MINC Frequently asked questions
Tools - MINC extra tools (registration, B0 correction, classification, etc)
VisualTools - Visual MINC tools (manual segmentation, registration, data visualisation)
Scripts - Extra scripts (typically perl) that have been collected over time
SoftwareDevelopment - Information on developing MINC software
Tutorials - Software development tutorials
Resources - Example data sets, library files, color maps, etc.
Atlases - The various atlases that are available from the BIC in the MINC format
Authors - The Authors of MINC and how to reference the tools