Difference between revisions of "Asymptote: Basics"

m (Syntax)
(Syntax)
 
(5 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
{{Asymptote}}
 
{{Asymptote}}
  
== IMPORTANT NOTE ==
 
Among us.
 
Thank you for reading this.
 
- Sombody
 
 
== Syntax ==
 
== Syntax ==
On the AoPS forums, you must start the Asymptote diagram with the [asy] tag and end with the [/asy] tag. Each command in Asymptote must be separated by a semicolon (;). This tells Asymptote where each command ends. For example, the command <tt>draw(A--B)</tt> draws a line segment from point <math>A</math> to <math>B</math> given as coordinate pairsThus, if you wanted to draw two line segments, say one of them from (0,0) to (50,50) (in units of PostScript points - see below for the explanation of units and size) and the other from (50,0) to (0,50), you can create the following document:
+
On AoPS, all Asymptote diagrams are declared with the "[asy]" tag and ended with the "[/asy]" tag. Each command in Asymptote must be separated by a semicolon (;), similar to programming languages like C and Java. This convention tells Asymptote where each command ends.  
draw((0,0)--(50,50));
+
 
draw((0,50)--(50,0));
+
 
 +
Commands do not necessarily need to be on separate lines, since semicolons are the only method by which Asymptote interprets new commandsHowever, putting the commands on separate lines is often useful to separate your commands to organize your code and improve readability for other AoPSers looking to interpret your code.  Whitespaces before and after commands are also not read by Asymptote, so any line can be indented as far as desired for clarity's sake.
 +
 
 +
 
 +
To write comments (Lines that are not interpreted by Asymptote), start a line with two forward slashes.
 +
 
 +
 
 +
Multi-line comments can be declared with /* and ended with */.
 +
 
 +
 
 +
Applying what we've learned, we can now write clear, legible, Asymptote code:
  
The two commands do not need to be on separate lines; it is the semicolon that separates them.  However, putting the commands on separate lines does not change the output, so it is often useful to separate your commands in this way in order to organize your code.  Whitespaces before and after commands are also not read by Asymptote, so any line can be indented as far as desired for clarity's sake.
 
  
To write comments in your code that do not affect the output at all, simply start a line with two forward slashes: <tt>//</tt> as in
+
  // The following line is drawn from (0,0) to (50,50)
+
/*
 +
This is a program
 +
that draws a triangle
 +
*/
 +
  //Below, we draw the first segment.
 
  draw((0,0)--(50,50));
 
  draw((0,0)--(50,50));
Multi-line comment can be declared with /* and ending in */.
+
//And the next two segments, written without a line break between them
/* The 
+
  draw((50,0)--(50,50));draw((50,0)--(0,0));
following line  
 
  is drawn from
 
(0,0) to (50,50) */
 
draw((0,0)--(50,50));
 
This is useful for finding where your mistakes are because you can comment out parts, and if it has a mistake, then the diagram will not produce an error.
 
  
 
==Variables and Data Types==
 
==Variables and Data Types==
Asymptote parses your code into substrings which have a certain '''data type''', for example a ''real'' (like <math>1.5</math>) or a ''pair'' (like <math>(2,3)</math>).  Each new variable that you declare must be declared as a data type that Asymptote recognizes, by the command <tt>[datatype] [variable];</tt>.  For example, if you wanted to declare the variable <math>n</math> to have type integer, you can use the command
+
When coding in Asymptote, it's often helpful to store data in '''data types'''. For example, a ''real'' number like <math>1.5</math> or a ''pair'' of numbers like <math>(2,3)</math>.  Each new variable that you create must be declared using a data type, with the command <tt>[datatype] [variable];</tt>.  For example, if you wanted to declare the variable <math>n</math> to have type integer, you can use the command
 
   int n;
 
   int n;
  
After it is declared, you can store a specific value in a variable using the <math>=</math> symbol, as in
+
After it's declared, you can store a specific value in a variable using the = symbol, as in
 
   n=3;
 
   n=3;
  
 
These two commands can be abbreviated by the single command <tt>int n=3;</tt>, and several integers can also be declared at once (<tt>int m,n,d;</tt>) or even many declarations and assignations at once: <tt>int a,b=2,c,d=5;</tt>.
 
These two commands can be abbreviated by the single command <tt>int n=3;</tt>, and several integers can also be declared at once (<tt>int m,n,d;</tt>) or even many declarations and assignations at once: <tt>int a,b=2,c,d=5;</tt>.
 
As another example of variable declaration, consider the picture of the X from the Syntax section above.  The same picture can be made as follows:
 
    pair A,B,C,D;
 
    A=(0,0);
 
    B=(50,50);
 
    C=(0,50);
 
    D=(50,0);
 
    draw(A--B);
 
    draw(C--D);
 
In this particular example, variable declarations made the code longer, but as you will see, declaring variables will significantly clean up your code in messier diagrams.
 
  
 
The most commonly used data types in Asymptote are given in the following table:
 
The most commonly used data types in Asymptote are given in the following table:

Latest revision as of 13:11, 5 July 2024

Asymptote (Vector Graphics Language)
Getting Started - Basics - Drawing - Labeling - Filling - Useful functions - Examples - Macros and Packages

Help - Reference - Advanced Asymptote - 3D Graphics - CSE5 Package - How to

Syntax

On AoPS, all Asymptote diagrams are declared with the "[asy]" tag and ended with the "[/asy]" tag. Each command in Asymptote must be separated by a semicolon (;), similar to programming languages like C and Java. This convention tells Asymptote where each command ends.


Commands do not necessarily need to be on separate lines, since semicolons are the only method by which Asymptote interprets new commands. However, putting the commands on separate lines is often useful to separate your commands to organize your code and improve readability for other AoPSers looking to interpret your code. Whitespaces before and after commands are also not read by Asymptote, so any line can be indented as far as desired for clarity's sake.


To write comments (Lines that are not interpreted by Asymptote), start a line with two forward slashes.


Multi-line comments can be declared with /* and ended with */.


Applying what we've learned, we can now write clear, legible, Asymptote code:


/*
This is a program
that draws a triangle
*/
//Below, we draw the first segment.
draw((0,0)--(50,50));
//And the next two segments, written without a line break between them
draw((50,0)--(50,50));draw((50,0)--(0,0));

Variables and Data Types

When coding in Asymptote, it's often helpful to store data in data types. For example, a real number like $1.5$ or a pair of numbers like $(2,3)$. Each new variable that you create must be declared using a data type, with the command [datatype] [variable];. For example, if you wanted to declare the variable $n$ to have type integer, you can use the command

 int n;

After it's declared, you can store a specific value in a variable using the = symbol, as in

 n=3;

These two commands can be abbreviated by the single command int n=3;, and several integers can also be declared at once (int m,n,d;) or even many declarations and assignations at once: int a,b=2,c,d=5;.

The most commonly used data types in Asymptote are given in the following table:

Table1.gif

Size and Unitsize

Asymptote is a primarily coordinate-based graphics language. Each point is a pair $(a,b)$ where $a$ is the $x$-coordinate and $b$ is the $y$-coordinate.

However, there are many ways to choose a Cartesian coordinate system for the plane; one must pick the placement of origin and the scale on each of the $x$- and $y$-axis. Asymptote will place your image in the center of your output page after it is drawn, so placement of origin is actually irrelevant. By default, the unit length in both the $x$ and $y$ directions is the PostScript bigpoint, which has length $1/72$ inches. Thus, if you do not change the scaling on the picture, the points $(0,0)$ and $(72,0)$ are exactly one inch apart when drawn in Asymptote. However, drawing in bigpoints is inconvenient if you wish to draw a figure that is exactly 3cm wide.

The function unitsize can be used to specify the unit length for your picture. This function takes up to 3 arguments: the picture you want to scale the axes for (if this isn't specified, it defaults to currentpicture, the picture you are drawing on), the unit length in the x direction, and the unit length in the y direction. If only one real argument is given, both the x and y unit sizes are set to this number. Thus the command

unitsize(72);

will tell Asymptote that from now on, your unit length is $1$ inch. Be careful when you are redefining your unit length - now that unitsize is set to $72$, the points $(0,0)$ and $(72,0)$ are actually $72$ inches apart!

Asymptote has the built-in constants pt (1/72.27 inches), inch, cm, and mm for convenience when defining lengths, so the above command can also be stated

unitsize(1inch);

The other useful function is size, which specifies the exact width and height of the box that your picture (if unspecified as a first argument, this will again default to currentpicture) will be fit into. If only one number is given, both the width and the height will be set to this number. For example, the command

size(5cm,5cm);

or just

size(5cm);

will fit the diagram to a 5cm x 5cm box regardless of the specified unitsizes.

As an example, make an Asymptote document containing the following two lines:

unitsize(2inch); 
draw(unitsquare);

and see what happens as you change the $2$ inch size to several other values.


Next: Drawing