Version: 1.8.1

Operators (B to C)

This file is automatically generated from java files. Do Not Edit It.

Definition

Operators in the GAML language are used to compose complex expressions. An operator performs a function on one, two, or n operands (which are other expressions and thus may be themselves composed of operators) and returns the result of this function.

Most of them use a classical prefixed functional syntax (i.e. operator_name(operand1, operand2, operand3), see below), with the exception of arithmetic (e.g. +, /), logical (and, or), comparison (e.g. >, <), access (., [..]) and pair (::) operators, which require an infixed notation (i.e. operand1 operator_symbol operand1).

The ternary functional if-else operator, ? :, uses a special infixed syntax composed with two symbols (e.g. operand1 ? operand2 : operand3). Two unary operators (- and !) use a traditional prefixed syntax that does not require parentheses unless the operand is itself a complex expression (e.g. - 10, ! (operand1 or operand2)).

Finally, special constructor operators ({...} for constructing points, [...] for constructing lists and maps) will require their operands to be placed between their two symbols (e.g. {1,2,3}, [operand1, operand2, ..., operandn] or [key1::value1, key2::value2... keyn::valuen]).

With the exception of these special cases above, the following rules apply to the syntax of operators:

if they only have one operand, the functional prefixed syntax is mandatory (e.g. operator_name(operand1))
if they have two arguments, either the functional prefixed syntax (e.g. operator_name(operand1, operand2)) or the infixed syntax (e.g. operand1 operator_name operand2) can be used.
if they have more than two arguments, either the functional prefixed syntax (e.g. operator_name(operand1, operand2, ..., operand)) or a special infixed syntax with the first operand on the left-hand side of the operator name (e.g. operand1 operator_name(operand2, ..., operand)) can be used.

All of these alternative syntaxes are completely equivalent.

Operators in GAML are purely functional, i.e. they are guaranteed to not have any side effects on their operands. For instance, the shuffle operator, which randomizes the positions of elements in a list, does not modify its list operand but returns a new shuffled list.

Priority between operators

The priority of operators determines, in the case of complex expressions composed of several operators, which one(s) will be evaluated first.

GAML follows in general the traditional priorities attributed to arithmetic, boolean, comparison operators, with some twists. Namely:

the constructor operators, like ::, used to compose pairs of operands, have the lowest priority of all operators (e.g. a > b :: b > c will return a pair of boolean values, which means that the two comparisons are evaluated before the operator applies. Similarly, [a > 10, b > 5] will return a list of boolean values.
it is followed by the ?: operator, the functional if-else (e.g. a > b ? a + 10 : a - 10 will return the result of the if-else).
next are the logical operators, and and or (e.g. a > b or b > c will return the value of the test)
next are the comparison operators (i.e. >, <, <=, >=, =, !=)
next the arithmetic operators in their logical order (multiplicative operators have a higher priority than additive operators)
next the unary operators - and !
next the access operators . and [] (e.g. {1,2,3}.x > 20 + {4,5,6}.y will return the result of the comparison between the x and y ordinates of the two points)
and finally the functional operators, which have the highest priority of all.

Using actions as operators

Actions defined in species can be used as operators, provided they are called on the correct agent. The syntax is that of normal functional operators, but the agent that will perform the action must be added as the first operand.

For instance, if the following species is defined:

species spec1 {
        int min(int x, int y) {
                return x > y ? x : y;
        }
}

Any agent instance of spec1 can use min as an operator (if the action conflicts with an existing operator, a warning will be emitted). For instance, in the same model, the following line is perfectly acceptable:

global {
        init {
                create spec1;
                spec1 my_agent <- spec1[0];
                int the_min <- my_agent min(10,20); // or min(my_agent, 10, 20);
        }
}

If the action doesn't have any operands, the syntax to use is my_agent the_action(). Finally, if it does not return a value, it might still be used but is considering as returning a value of type unknown (e.g. unknown result <- my_agent the_action(op1, op2);).

Note that due to the fact that actions are written by modelers, the general functional contract is not respected in that case: actions might perfectly have side effects on their operands (including the agent).

Operators by categories

Dates

Displays

horizontal, stack, vertical,

Driving operators

as_driving_graph,

edge

edge_between, strahler,

diff, diff2,

crs, csv_file, dxf_file, evaluate_sub_model, file_exists, folder, folder_exists, gaml_file, geojson_file, get, gif_file, gml_file, grid_file, image_file, is_csv, is_dxf, is_gaml, is_geojson, is_gif, is_gml, is_grid, is_image, is_json, is_obj, is_osm, is_pgm, is_property, is_R, is_saved_simulation, is_shape, is_svg, is_text, is_threeds, is_xml, json_file, new_folder, obj_file, osm_file, pgm_file, property_file, R_file, read, saved_simulation_file, shape_file, step_sub_model, svg_file, text_file, threeds_file, writable, xml_file,

conversation, message,

GamaMetaType

type_of,

add_edge, add_node, adjacency, agent_from_geometry, all_pairs_shortest_path, alpha_index, as_distance_graph, as_edge_graph, as_intersection_graph, as_path, beta_index, betweenness_centrality, biggest_cliques_of, connected_components_of, connectivity_index, contains_edge, contains_vertex, degree_of, directed, edge, edge_between, edge_betweenness, edges, gamma_index, generate_barabasi_albert, generate_complete_graph, generate_watts_strogatz, grid_cells_to_graph, in_degree_of, in_edges_of, layout_circle, layout_force, layout_grid, load_graph_from_file, load_shortest_paths, main_connected_component, max_flow_between, maximal_cliques_of, nb_cycles, neighbors_of, node, nodes, out_degree_of, out_edges_of, path_between, paths_between, predecessors_of, remove_node_from, rewire_n, source_of, spatial_graph, strahler, successors_of, sum, target_of, undirected, use_cache, weight_of, with_optimizer_type, with_weights,

as_4_grid, as_grid, as_hexagonal_grid, grid_at, path_between,

Iterator operators

accumulate, all_match, as_map, collect, count, create_map, first_with, frequency_of, group_by, index_by, last_with, max_of, mean_of, min_of, none_matches, one_matches, product_of, sort_by, sum_of, variance_of, where, with_max_of, with_min_of,

all_indexes_of, copy_between, index_of, last_index_of,

Logical operators

:, !, ?, add_3Dmodel, add_geometry, add_icon, and, or, xor,

Map comparaison operators

fuzzy_kappa, fuzzy_kappa_sim, kappa, kappa_sim, percent_absolute_deviation,

as_map, create_map, index_of, last_index_of,

Material

material,

-, /, ., *, +, append_horizontally, append_vertically, column_at, columns_list, determinant, eigenvalues, index_of, inverse, last_index_of, row_at, rows_list, shuffle, trace, transpose,

multicriteria operators

electre_DM, evidence_theory_DM, fuzzy_choquet_DM, promethee_DM, weighted_means_DM,

agent_from_geometry, all_pairs_shortest_path, as_path, load_shortest_paths, max_flow_between, path_between, path_to, paths_between, use_cache,

-, /, *, +, <, <=, >, >=, add_point, angle_between, any_location_in, centroid, closest_points_with, farthest_point_to, grid_at, norm, points_along, points_at, points_on,

Random operators

binomial, flip, gamma_density, gamma_rnd, gamma_trunc_rnd, gauss, lognormal_density, lognormal_rnd, lognormal_trunc_rnd, open_simplex_generator, poisson, rnd, rnd_choice, sample, shuffle, simplex_generator, skew_gauss, truncated_gauss, weibull_density, weibull_rnd, weibull_trunc_rnd,

ReverseOperators

restore_simulation, restore_simulation_from_file, save_agent, save_simulation, serialize, serialize_agent,

Shape

arc, box, circle, cone, cone3D, cross, cube, curve, cylinder, ellipse, elliptical_arc, envelope, geometry_collection, hexagon, line, link, plan, polygon, polyhedron, pyramid, rectangle, sphere, square, squircle, teapot, triangle,

Spatial operators

-, *, +, add_point, agent_closest_to, agent_farthest_to, agents_at_distance, agents_inside, agents_overlapping, angle_between, any_location_in, arc, around, as_4_grid, as_grid, as_hexagonal_grid, at_distance, at_location, box, centroid, circle, clean, clean_network, closest_points_with, closest_to, cone, cone3D, convex_hull, covers, cross, crosses, crs, CRS_transform, cube, curve, cylinder, dem, direction_between, disjoint_from, distance_between, distance_to, ellipse, elliptical_arc, envelope, farthest_point_to, farthest_to, geometry_collection, gini, hexagon, hierarchical_clustering, IDW, inside, inter, intersects, inverse_rotation, line, link, masked_by, moran, neighbors_at, neighbors_of, normalized_rotation, overlapping, overlaps, partially_overlaps, path_between, path_to, plan, points_along, points_at, points_on, polygon, polyhedron, pyramid, rectangle, rotated_by, rotation_composition, round, scaled_to, set_z, simple_clustering_by_distance, simplification, skeletonize, smooth, sphere, split_at, split_geometry, split_lines, square, squircle, teapot, to_GAMA_CRS, to_rectangles, to_segments, to_squares, to_sub_geometries, touches, towards, transformed_by, translated_by, triangle, triangulate, union, using, voronoi, with_precision, without_holes,

Spatial properties operators

covers, crosses, intersects, partially_overlaps, touches,

Spatial queries operators

agent_closest_to, agent_farthest_to, agents_at_distance, agents_inside, agents_overlapping, at_distance, closest_to, farthest_to, inside, neighbors_at, neighbors_of, overlapping,

Spatial relations operators

direction_between, distance_between, distance_to, path_between, path_to, towards,

Spatial statistical operators

hierarchical_clustering, simple_clustering_by_distance,

Spatial transformations operators

-, *, +, as_4_grid, as_grid, as_hexagonal_grid, at_location, clean, clean_network, convex_hull, CRS_transform, inverse_rotation, normalized_rotation, rotated_by, rotation_composition, scaled_to, simplification, skeletonize, smooth, split_geometry, split_lines, to_GAMA_CRS, to_rectangles, to_segments, to_squares, to_sub_geometries, transformed_by, translated_by, triangulate, voronoi, with_precision, without_holes,

index_of, last_index_of, of_generic_species, of_species,

Statistical operators

auto_correlation, beta, binomial_coeff, binomial_complemented, binomial_sum, build, chi_square, chi_square_complemented, corR, correlation, covariance, dbscan, distribution_of, distribution2d_of, dtw, durbin_watson, frequency_of, gamma, gamma_distribution, gamma_distribution_complemented, geometric_mean, gini, harmonic_mean, hierarchical_clustering, incomplete_beta, incomplete_gamma, incomplete_gamma_complement, kmeans, kurtosis, kurtosis, log_gamma, max, mean, mean_deviation, meanR, median, min, moment, moran, mul, normal_area, normal_density, normal_inverse, predict, pValue_for_fStat, pValue_for_tStat, quantile, quantile_inverse, rank_interpolated, rms, simple_clustering_by_distance, skew, skewness, split, split_in, split_using, standard_deviation, student_area, student_t_inverse, sum, variance, variance,

+, <, <=, >, >=, at, char, contains, contains_all, contains_any, copy_between, date, empty, first, in, indented_by, index_of, is_number, last, last_index_of, length, lower_case, replace, replace_regex, reverse, sample, shuffle, split_with, string, upper_case,

SubModel

load_sub_model,

System

., choose, command, copy, copy_to_clipboard, dead, enter, eval_gaml, every, is_error, is_warning, user_input,

date, string,

action, agent, attributes, BDIPlan, bool, container, emotion, file, float, gaml_type, geometry, graph, int, kml, list, map, material, matrix, mental_state, Norm, pair, path, point, predicate, regression, rgb, Sanction, skill, social_link, topology, unknown,

User control operators

choose, enter, user_input,

Operators

`BDIPlan`

Possible use:

BDIPlan (any) ---> BDIPlan

Result:

`before`

Possible use:

before (date) ---> bool
any expression before date ---> bool
before (any expression , date) ---> bool

Result:

Returns true if the current_date of the model is strictly before the date passed in argument. Synonym of 'current_date < argument'

Examples:

 
reflex when: before(starting_date) {} 	// this reflex will never be run

`beta`

Possible use:

float beta float ---> float
beta (float , float) ---> float

Result:

Returns the beta function with arguments a, b.

Comment:

Checked on R. beta(4,5)

Examples:

 
float var0 <- beta(4,5) with_precision(4); // var0 equals 0.0036

`beta_index`

Possible use:

beta_index (graph) ---> float

Result:

returns the beta index of the graph (Measures the level of connectivity in a graph and is expressed by the relationship between the number of links (e) over the number of nodes (v) : beta = e/v.

Examples:

 
graph graphEpidemio <- graph([]); 
float var1 <- beta_index(graphEpidemio); // var1 equals the beta index of the graph

`between`

Possible use:

date between date ---> bool
between (date , date) ---> bool
between (date, date, date) ---> bool
between (any expression, date, date) ---> bool
between (float, float, float) ---> bool
between (int, int, int) ---> bool

Result:

returns true if the first float operand is bigger than the second float operand and smaller than the third float operand returns true the first integer operand is bigger than the second integer operand and smaller than the third integer operand

Special cases:

returns true if the first operand is between the two dates passed in arguments (both exclusive). Can be combined with 'every' to express a frequency between two dates

 
bool var0 <- (date('2016-01-01') between(date('2000-01-01'), date('2020-02-02'))); // var0 equals true 
// will return true every new day between these two dates, taking the first one as the starting point 
every(#day between(date('2000-01-01'), date('2020-02-02'))) 

returns true if the first operand is between the two dates passed in arguments (both exclusive). The version with 2 arguments compares the current_date with the 2 others

 
bool var3 <- (date('2016-01-01') between(date('2000-01-01'), date('2020-02-02'))); // var3 equals true 
// // will return true if the current_date of the model is in_between the 2 
between(date('2000-01-01'), date('2020-02-02'))

Examples:

 
bool var6 <- between(5.0, 1.0, 10.0); // var6 equals true 
bool var7 <- between(5, 1, 10); // var7 equals true

`betweenness_centrality`

Possible use:

betweenness_centrality (graph) ---> map

Result:

returns a map containing for each vertex (key), its betweenness centrality (value): number of shortest paths passing through each vertex

Examples:

 
graph graphEpidemio <- graph([]); 
map var1 <- betweenness_centrality(graphEpidemio); // var1 equals the betweenness centrality index of the graph

`biggest_cliques_of`

Possible use:

biggest_cliques_of (graph) ---> list<list>

Result:

returns the biggest cliques of a graph using the Bron-Kerbosch clique detection algorithm

Examples:

 
graph my_graph <- graph([]); 
list<list> var1 <- biggest_cliques_of (my_graph); // var1 equals the list of the biggest cliques as list

`binomial`

Possible use:

int binomial float ---> int
binomial (int , float) ---> int

Result:

A value from a random variable following a binomial distribution. The operands represent the number of experiments n and the success probability p.

Comment:

The binomial distribution is the discrete probability distribution of the number of successes in a sequence of n independent yes/no experiments, each of which yields success with probability p, cf. Binomial distribution on Wikipedia.

Examples:

 
int var0 <- binomial(15,0.6); // var0 equals a random positive integer

`binomial_coeff`

Possible use:

int binomial_coeff int ---> float
binomial_coeff (int , int) ---> float

Result:

Returns n choose k as a double. Note the integerization of the double return value.

Examples:

 
float var0 <- binomial_coeff(10,2); // var0 equals 45

`binomial_complemented`

Possible use:

binomial_complemented (int, int, float) ---> float

Result:

Returns the sum of the terms k+1 through n of the Binomial probability density, where n is the number of trials and P is the probability of success in the range 0 to 1.

Examples:

 
float var0 <- binomial_complemented(10,5,0.5) with_precision(2); // var0 equals 0.38

`binomial_sum`

Possible use:

binomial_sum (int, int, float) ---> float

Result:

Returns the sum of the terms 0 through k of the Binomial probability density, where n is the number of trials and p is the probability of success in the range 0 to 1.

Examples:

 
float var0 <- binomial_sum(5,10,0.5) with_precision(2); // var0 equals 0.62

`blend`

Possible use:

rgb blend rgb ---> rgb
blend (rgb , rgb) ---> rgb
blend (rgb, rgb, float) ---> rgb

Result:

Blend two colors with an optional ratio (c1 * r + c2 * (1 - r)) between 0 and 1

Special cases:

If the ratio is omitted, an even blend is done

 
rgb var3 <- blend(#red, #blue); // var3 equals to a color very close to the purple

Examples:

 
rgb var1 <- blend(#red, #blue, 0.3); // var1 equals to a color between the purple and the blue

`bool`

Possible use:

bool (any) ---> bool

Result:

`box`

Possible use:

box (point) ---> geometry
box (float, float, float) ---> geometry

Result:

A box geometry which side sizes are given by the operands.

Comment:

the center of the box is by default the location of the current agent in which has been called this operator.the center of the box is by default the location of the current agent in which has been called this operator.

Special cases:

returns nil if the operand is nil.
returns nil if the operand is nil.

Examples:

 
geometry var0 <- box(10, 5 , 5); // var0 equals a geometry as a rectangle with width = 10, height = 5 depth= 5. 
geometry var1 <- box({10, 5 , 5}); // var1 equals a geometry as a rectangle with width = 10, height = 5 depth= 5. 
float var2 <-  (box({10, 10 , 5}) at_location point(50,50,0)).location.y; // var2 equals 50.0

`brewer_colors`

Possible use:

brewer_colors (string) ---> list<rgb>
string brewer_colors int ---> list<rgb>
brewer_colors (string , int) ---> list<rgb>

Result:

Build a list of colors of a given type (see website http://colorbrewer2.org/). The list of palettes can be obtained by calling brewer_palettes Build a list of colors of a given type (see website http://colorbrewer2.org/) with a given number of classes

Examples:

 
list<rgb> var0 <- list<rgb> colors <- brewer_colors("OrRd");; // var0 equals a list of 6 blue colors 
list<rgb> var1 <- list<rgb> colors <- brewer_colors("Pastel1", 5);; // var1 equals a list of 5 sequential colors in the palette named 'Pastel1'. The list of palettes can be obtained by calling brewer_palettes

`brewer_palettes`

Possible use:

brewer_palettes (int) ---> list<string>
int brewer_palettes int ---> list<string>
brewer_palettes (int , int) ---> list<string>

Result:

returns the list a palette with a given min number of classes) returns the list a palette with a given min number of classes and max number of classes)

Examples:

 
list<string> var0 <- list<string> palettes <- brewer_palettes(3);; // var0 equals a list of palettes that are composed of a min of 3 colors 
list<string> var1 <- list<string> palettes <- brewer_palettes(5,10);; // var1 equals a list of palettes that are composed of a min of 5 colors and a max of 10 colors

`buffer`

Same signification as +

`build`

Possible use:

build (matrix) ---> regression

Result:

returns the regression build from the matrix data (a row = an instance, the last value of each line is the y value) while using the given ordinary least squares method. Usage: build(data)

Examples:

 
build(matrix([[1.0,2.0,3.0,4.0],[2.0,3.0,4.0,2.0]]))

`ceil`

Possible use:

ceil (float) ---> float

Result:

Maps the operand to the smallest following integer, i.e. the smallest integer not less than x.

Examples:

 
float var0 <- ceil(3); // var0 equals 3.0 
float var1 <- ceil(3.5); // var1 equals 4.0 
float var2 <- ceil(-4.7); // var2 equals -4.0

`centroid`

Possible use:

centroid (geometry) ---> point

Result:

Centroid (weighted sum of the centroids of a decomposition of the area into triangles) of the operand-geometry. Can be different to the location of the geometry

Examples:

 
point var0 <- centroid(world); // var0 equals the centroid of the square, for example : {50.0,50.0}.

`char`

Possible use:

char (int) ---> string

Special cases:

converts ACSII integer value to character

 
string var0 <- char (34); // var0 equals '"'

`chi_square`

Possible use:

float chi_square float ---> float
chi_square (float , float) ---> float

Result:

Returns the area under the left hand tail (from 0 to x) of the Chi square probability density function with df degrees of freedom.

Examples:

 
float var0 <- chi_square(20.0,10) with_precision(3); // var0 equals 0.971

`chi_square_complemented`

Possible use:

float chi_square_complemented float ---> float
chi_square_complemented (float , float) ---> float

Result:

Returns the area under the right hand tail (from x to infinity) of the Chi square probability density function with df degrees of freedom.

Examples:

 
float var0 <- chi_square_complemented(2,10) with_precision(3); // var0 equals 0.996

`choose`

Possible use:

choose (string, any GAML type, unknown, list) ---> msi.gama.kernel.experiment.IParameter

Result:

Allows the user to choose a value by specifying a title, a type, and a list of possible values

`circle`

Possible use:

circle (float) ---> geometry
float circle point ---> geometry
circle (float , point) ---> geometry

Result:

A circle geometry which radius is equal to the operand. A circle geometry which radius is equal to the first operand, and the center has the location equal to the second operand.

Comment:

the center of the circle is by default the location of the current agent in which has been called this operator.

Special cases:

returns a point if the operand is lower or equal to 0.
returns a point if the operand is lower or equal to 0.

Examples:

 
geometry var0 <- circle(10); // var0 equals a geometry as a circle of radius 10. 
geometry var1 <- circle(10,{80,30}); // var1 equals a geometry as a circle of radius 10, the center will be in the location {80,30}.

`clean`

Possible use:

clean (geometry) ---> geometry

Result:

A geometry corresponding to the cleaning of the operand (geometry, agent, point)

Comment:

The cleaning corresponds to a buffer with a distance of 0.0

Examples:

 
geometry var0 <- clean(self); // var0 equals returns the geometry resulting from the cleaning of the geometry of the agent applying the operator.

`clean_network`

Possible use:

clean_network (list<geometry>, float, bool, bool) ---> list<geometry>

Result:

A list of polylines corresponding to the cleaning of the first operand (list of polyline geometry or agents), considering the tolerance distance given by the second operand; the third operator is used to define if the operator should as well split the lines at their intersections(true to split the lines); the last operandis used to specify if the operator should as well keep only the main connected component of the network. Usage: clean_network(lines:list of geometries or agents, tolerance: float, split_lines: bool, keepMainConnectedComponent: bool)

Comment:

The cleaned set of polylines

Examples:

 
list<geometry> var0 <- clean_network(my_road_shapefile.contents, 1.0, true, false); // var0 equals returns the list of polulines resulting from the cleaning of the geometry of the agent applying the operator with a tolerance of 1m, and splitting the lines at their intersections. 
list<geometry> var1 <- clean_network([line({10,10}, {20,20}), line({10,20},{20,10})],3.0,true,false); // var1 equals [line({10.0,20.0,0.0},{15.0,15.0,0.0}),line({15.0,15.0,0.0},{20.0,10.0,0.0}), line({10.0,10.0,0.0},{15.0,15.0,0.0}), line({15.0,15.0,0.0},{20.0,20.0,0.0})]

`closest_points_with`

Possible use:

geometry closest_points_with geometry ---> list<point>
closest_points_with (geometry , geometry) ---> list<point>

Result:

A list of two closest points between the two geometries.

Examples:

 
list<point> var0 <- geom1 closest_points_with(geom2); // var0 equals [pt1, pt2] with pt1 the closest point of geom1 to geom2 and pt1 the closest point of geom2 to geom1

`closest_to`

Possible use:

container<unknown,geometry> closest_to geometry ---> geometry
closest_to (container<unknown,geometry> , geometry) ---> geometry
closest_to (container<unknown,geometry>, geometry, int) ---> list<geometry>

Result:

The N agents or geometries among the left-operand list of agents, species or meta-population (addition of species), that are the closest to the operand (casted as a geometry). An agent or a geometry among the left-operand list of agents, species or meta-population (addition of species), the closest to the operand (casted as a geometry).

Comment:

the distance is computed in the topology of the calling agent (the agent in which this operator is used), with the distance algorithm specific to the topology.the distance is computed in the topology of the calling agent (the agent in which this operator is used), with the distance algorithm specific to the topology.

Examples:

 
list<geometry> var0 <- [ag1, ag2, ag3] closest_to(self, 2); // var0 equals return the 2 closest agents among ag1, ag2 and ag3 to the agent applying the operator. 
(species1 + species2) closest_to (self, 5) 
geometry var2 <- [ag1, ag2, ag3] closest_to(self); // var2 equals return the closest agent among ag1, ag2 and ag3 to the agent applying the operator. 
(species1 + species2) closest_to self

`collect`

Possible use:

container collect any expression ---> list
collect (container , any expression) ---> list

Result:

returns a new list, in which each element is the evaluation of the right-hand operand.

Comment:

collect is similar to accumulate except that accumulate always produces flat lists if the right-hand operand returns a list.In addition, collect can be applied to any container.

Special cases:

if the left-hand operand is nil, collect throws an error

Examples:

 
list var0 <- [1,2,4] collect (each *2); // var0 equals [2,4,8] 
list var1 <- [1,2,4] collect ([2,4]); // var1 equals [[2,4],[2,4],[2,4]] 
list var2 <- [1::2, 3::4, 5::6] collect (each + 2); // var2 equals [4,6,8] 
list var3 <- (list(node) collect (node(each).location.x * 2); // var3 equals the list of nodes with their x multiplied by 2

`column_at`

Possible use:

matrix<unknown> column_at int ---> list<unknown>
column_at (matrix<unknown> , int) ---> list<unknown>

Result:

returns the column at a num_col (right-hand operand)

Examples:

 
list<unknown> var0 <- matrix([["el11","el12","el13"],["el21","el22","el23"],["el31","el32","el33"]]) column_at 2; // var0 equals ["el31","el32","el33"]

`columns_list`

Possible use:

columns_list (matrix<unknown>) ---> list<list<unknown>>

Result:

returns a list of the columns of the matrix, with each column as a list of elements

Examples:

 
list<list<unknown>> var0 <- columns_list(matrix([["el11","el12","el13"],["el21","el22","el23"],["el31","el32","el33"]])); // var0 equals [["el11","el12","el13"],["el21","el22","el23"],["el31","el32","el33"]]

`command`

Possible use:

command (string) ---> string
string command string ---> string
command (string , string) ---> string
command (string, string, map<string,string>) ---> string

Result:

command allows GAMA to issue a system command using the system terminal or shell and to receive a string containing the outcome of the command or script executed. By default, commands are blocking the agent calling them, unless the sequence ' &' is used at the end. In this case, the result of the operator is an empty string. The basic form with only one string in argument uses the directory of the model and does not set any environment variables. Two other forms (with a directory and a map<string, string> of environment variables) are available. command allows GAMA to issue a system command using the system terminal or shell and to receive a string containing the outcome of the command or script executed. By default, commands are blocking the agent calling them, unless the sequence ' &' is used at the end. In this case, the result of the operator is an empty string command allows GAMA to issue a system command using the system terminal or shell and to receive a string containing the outcome of the command or script executed. By default, commands are blocking the agent calling them, unless the sequence ' &' is used at the end. In this case, the result of the operator is an empty string. The basic form with only one string in argument uses the directory of the model and does not set any environment variables. Two other forms (with a directory and a map<string, string> of environment variables) are available.

`cone`

Possible use:

cone (point) ---> geometry
int cone int ---> geometry
cone (int , int) ---> geometry

Result:

A cone geometry which min and max angles are given by the operands. A cone geometry which min and max angles are given by the operands.

Comment:

the center of the cone is by default the location of the current agent in which has been called this operator.the center of the cone is by default the location of the current agent in which has been called this operator.

Special cases:

returns nil if the operand is nil.
returns nil if the operand is nil.

Examples:

 
geometry var0 <- cone({0, 45}); // var0 equals a geometry as a cone with min angle is 0 and max angle is 45. 
geometry var1 <- cone(0, 45); // var1 equals a geometry as a cone with min angle is 0 and max angle is 45.

`cone3D`

Possible use:

float cone3D float ---> geometry
cone3D (float , float) ---> geometry

Result:

A cone geometry which base radius size is equal to the first operand, and which the height is equal to the second operand.

Comment:

the center of the cone is by default the location of the current agent in which has been called this operator.

Special cases:

returns a point if the operand is lower or equal to 0.

Examples:

 
geometry var0 <- cone3D(10.0,5.0); // var0 equals a geometry as a cone with a base circle of radius 10 and a height of 5.

`connected_components_of`

Possible use:

connected_components_of (graph) ---> list<list>
graph connected_components_of bool ---> list<list>
connected_components_of (graph , bool) ---> list<list>

Result:

returns the connected components of a graph, i.e. the list of all edges (if the boolean is true) or vertices (if the boolean is false) that are in the connected components. returns the connected components of a graph, i.e. the list of all vertices that are in the maximally connected component together with the specified vertex.

Examples:

 
graph my_graph2 <- graph([]); 
list<list> var1 <- connected_components_of (my_graph2, true); // var1 equals the list of all the components as list 
graph my_graph <- graph([]); 
list<list> var3 <- connected_components_of (my_graph); // var3 equals the list of all the components as list

`connectivity_index`

Possible use:

connectivity_index (graph) ---> float

Result:

returns a simple connectivity index. This number is estimated through the number of nodes (v) and of sub-graphs (p) : IC = (v - p) /(v - 1).

Examples:

 
graph graphEpidemio <- graph([]); 
float var1 <- connectivity_index(graphEpidemio); // var1 equals the connectivity index of the graph

`container`

Possible use:

container (any) ---> container

`contains`

Possible use:

container<KeyType,ValueType> contains unknown ---> bool
contains (container<KeyType,ValueType> , unknown) ---> bool
string contains string ---> bool
contains (string , string) ---> bool

Result:

true, if the container contains the right operand, false otherwise. 'contains' can also be written 'contains_value'. On graphs, it is equivalent to calling 'contains_edge'

Comment:

the contains operator behavior depends on the nature of the operand

Special cases:

if it is a map, contains, which can also be written 'contains_value', returns true if the operand is a value of the map
if it is a pair, contains_key returns true if the operand is equal to the value of the pair
if it is a file, contains returns true it the operand is contained in the file content
if it is a population, contains returns true if the operand is an agent of the population, false otherwise
if it is a graph, contains can be written 'contains_edge' and returns true if the operand is an edge of the graph, false otherwise (use 'contains_node' for testing the presence of a node)
if both operands are strings, returns true if the right-hand operand contains the right-hand pattern;
if it is a list or a matrix, contains returns true if the list or matrix contains the right operand

 
bool var0 <- [1, 2, 3] contains 2; // var0 equals true 
bool var1 <- [{1,2}, {3,4}, {5,6}] contains {3,4}; // var1 equals true

Examples:

 
bool var2 <- 'abcded' contains 'bc'; // var2 equals true

`contains_all`

Possible use:

string contains_all list ---> bool
contains_all (string , list) ---> bool
container contains_all container ---> bool
contains_all (container , container) ---> bool

Result:

true if the left operand contains all the elements of the right operand, false otherwise

Comment:

the definition of contains depends on the container

Special cases:

if the right operand is nil or empty, contains_all returns true
if the left-operand is a string, test whether the string contains all the element of the list;

 
bool var0 <- "abcabcabc" contains_all ["ca","xy"]; // var0 equals false

Examples:

 
bool var1 <- [1,2,3,4,5,6] contains_all [2,4]; // var1 equals true  
bool var2 <- [1,2,3,4,5,6] contains_all [2,8]; // var2 equals false 
bool var3 <- [1::2, 3::4, 5::6] contains_all [1,3]; // var3 equals false  
bool var4 <- [1::2, 3::4, 5::6] contains_all [2,4]; // var4 equals true

`contains_any`

Possible use:

string contains_any list ---> bool
contains_any (string , list) ---> bool
container contains_any container ---> bool
contains_any (container , container) ---> bool

Result:

true if the left operand contains one of the elements of the right operand, false otherwise

Comment:

the definition of contains depends on the container

Special cases:

if the right operand is nil or empty, contains_any returns false

Examples:

 
bool var0 <- "abcabcabc" contains_any ["ca","xy"]; // var0 equals true 
bool var1 <- [1,2,3,4,5,6] contains_any [2,4]; // var1 equals true  
bool var2 <- [1,2,3,4,5,6] contains_any [2,8]; // var2 equals true 
bool var3 <- [1::2, 3::4, 5::6] contains_any [1,3]; // var3 equals false 
bool var4 <- [1::2, 3::4, 5::6] contains_any [2,4]; // var4 equals true

`contains_edge`

Possible use:

graph contains_edge pair ---> bool
contains_edge (graph , pair) ---> bool
graph contains_edge unknown ---> bool
contains_edge (graph , unknown) ---> bool

Result:

returns true if the graph(left-hand operand) contains the given edge (righ-hand operand), false otherwise

Special cases:

if the left-hand operand is nil, returns false
if the right-hand operand is a pair, returns true if it exists an edge between the two elements of the pair in the graph

 
bool var0 <- graphEpidemio contains_edge (node(0)::node(3)); // var0 equals true

Examples:

 
graph graphFromMap <-  as_edge_graph([{1,5}::{12,45},{12,45}::{34,56}]); 
bool var2 <- graphFromMap contains_edge link({1,5},{12,45}); // var2 equals true

`contains_key`

Possible use:

container<KeyType,ValueType> contains_key unknown ---> bool
contains_key (container<KeyType,ValueType> , unknown) ---> bool

Result:

true, if the left-hand operand -- the container -- contains a key -- or an index -- equal to the right-hand operand, false otherwise. On graphs, 'contains_key' is equivalent to calling 'contains_vertex'

Comment:

the behavior of contains_key depends on the nature of the container

Special cases:

if it is a map, contains_key returns true if the operand is a key of the map
if it is a pair, contains_key returns true if the operand is equal to the key of the pair
if it is a matrix, contains_key returns true if the point operand is a valid index of the matrix (i.e. >= {0,0} and < {rows, col})
if it is a file, contains_key is applied to the file contents -- a container
if it is a graph, contains_key returns true if the graph contains the corresponding vertex
if it is a list, contains_key returns true if the right-hand operand is an integer and if it is a valid index (i.e. >= 0 and < length)

 
bool var0 <- [1, 2, 3] contains_key 3; // var0 equals false 
bool var1 <- [{1,2}, {3,4}, {5,6}] contains_key 0; // var1 equals true

`contains_node`

Same signification as contains_key

`contains_value`

Same signification as contains

`contains_vertex`

Possible use:

graph contains_vertex unknown ---> bool
contains_vertex (graph , unknown) ---> bool

Result:

returns true if the graph(left-hand operand) contains the given vertex (righ-hand operand), false otherwise

Special cases:

if the left-hand operand is nil, returns false

Examples:

 
graph graphFromMap<-  as_edge_graph([{1,5}::{12,45},{12,45}::{34,56}]); 
bool var1 <- graphFromMap contains_vertex {1,5}; // var1 equals true

`conversation`

Possible use:

conversation (unknown) ---> conversation

`convex_hull`

Possible use:

convex_hull (geometry) ---> geometry

Result:

A geometry corresponding to the convex hull of the operand.

Examples:

 
geometry var0 <- convex_hull(self); // var0 equals the convex hull of the geometry of the agent applying the operator

`copy`

Possible use:

copy (unknown) ---> unknown

Result:

returns a copy of the operand.

`copy_between`

Possible use:

copy_between (string, int, int) ---> string
copy_between (list, int, int) ---> list

Result:

Returns a copy of the first operand between the indexes determined by the second (inclusive) and third operands (exclusive)

Special cases:

If the first operand is empty, returns an empty object of the same type
If the second operand is greater than or equal to the third operand, return an empty object of the same type
If the first operand is nil, raises an error

Examples:

 
string var0 <- copy_between("abcabcabc", 2,6); // var0 equals "cabc" 
list var1 <-  copy_between ([4, 1, 6, 9 ,7], 1, 3); // var1 equals [1, 6]

`copy_to_clipboard`

Possible use:

copy_to_clipboard (string) ---> bool

Result:

Tries to copy the text in parameter to the clipboard and returns whether it has been correctly copied or not (for instance it might be impossible in a headless environment)

Examples:

 
bool copied  <- copy_to_clipboard('text to copy');

`corR`

Possible use:

container corR container ---> unknown
corR (container , container) ---> unknown

Result:

returns the Pearson correlation coefficient of two given vectors (right-hand operands) in given variable (left-hand operand).

Special cases:

if the lengths of two vectors in the right-hand aren't equal, returns 0

Examples:

 
list X <- [1, 2, 3]; 
list Y <- [1, 2, 4]; 
unknown var2 <- corR(X, Y); // var2 equals 0.981980506061966

`correlation`

Possible use:

container correlation container ---> float
correlation (container , container) ---> float

Result:

Returns the correlation of two data sequences (having the same size)

Examples:

 
float var0 <- correlation([1,2,1,3,1,2], [1,2,1,3,1,2]) with_precision(4); // var0 equals 1.2 
float var1 <- correlation([13,2,1,4,1,2], [1,2,1,3,1,2]) with_precision(2); // var1 equals -0.21

`cos`

Possible use:

cos (float) ---> float
cos (int) ---> float

Result:

Returns the value (in [-1,1]) of the cosinus of the operand (in decimal degrees). The argument is casted to an int before being evaluated.

Special cases:

Operand values out of the range [0-359] are normalized.

Examples:

 
float var0 <- cos (0.0); // var0 equals 1.0 
float var1 <- cos(360.0); // var1 equals 1.0 
float var2 <- cos(-720.0); // var2 equals 1.0 
float var3 <- cos (0); // var3 equals 1.0 
float var4 <- cos(360); // var4 equals 1.0 
float var5 <- cos(-720); // var5 equals 1.0

`cos_rad`

Possible use:

cos_rad (float) ---> float

Result:

Returns the value (in [-1,1]) of the cosinus of the operand (in radians).

Special cases:

Operand values out of the range [0-359] are normalized.

Examples:

 
float var0 <- cos_rad(0.0); // var0 equals 1.0 
float var1 <- cos_rad(#pi); // var1 equals -1.0

`count`

Possible use:

container count any expression ---> int
count (container , any expression) ---> int

Result:

returns an int, equal to the number of elements of the left-hand operand that make the right-hand operand evaluate to true.

Comment:

in the right-hand operand, the keyword each can be used to represent, in turn, each of the elements.

Special cases:

if the left-hand operand is nil, count throws an error

Examples:

 
int var0 <- [1,2,3,4,5,6,7,8] count (each > 3); // var0 equals 5 
// Number of nodes of graph g2 without any out edge 
graph g2 <- graph([]); 
int var3 <- g2 count (length(g2 out_edges_of each) = 0  ) ; // var3 equals the total number of out edges 
// Number of agents node with x > 32 
int n <- (list(node) count (round(node(each).location.x) > 32); 
int var6 <- [1::2, 3::4, 5::6] count (each > 4); // var6 equals 1

`covariance`

Possible use:

container covariance container ---> float
covariance (container , container) ---> float

Result:

Returns the covariance of two data sequences

Examples:

 
float var0 <- covariance([13,2,1,4,1,2], [1,2,1,3,1,2]) with_precision(2); // var0 equals -0.67

`covers`

Possible use:

geometry covers geometry ---> bool
covers (geometry , geometry) ---> bool

Result:

A boolean, equal to true if the left-geometry (or agent/point) covers the right-geometry (or agent/point).

Special cases:

if one of the operand is null, returns false.

Examples:

 
bool var0 <- square(5) covers square(2); // var0 equals true

`create_map`

Possible use:

list create_map list ---> map
create_map (list , list) ---> map

Result:

returns a new map using the left operand as keys for the right operand

Special cases:

if the left operand contains duplicates, create_map throws an error.
if both operands have different lengths, choose the minimum length between the two operandsfor the size of the map

Examples:

 
map<int,string> var0 <- create_map([0,1,2],['a','b','c']); // var0 equals [0::'a',1::'b',2::'c'] 
map<int,float> var1 <- create_map([0,1],[0.1,0.2,0.3]); // var1 equals [0::0.1,1::0.2] 
map<string,float> var2 <- create_map(['a','b','c','d'],[1.0,2.0,3.0]); // var2 equals ['a'::1.0,'b'::2.0,'c'::3.0]

`cross`

Possible use:

cross (float) ---> geometry
float cross float ---> geometry
cross (float , float) ---> geometry

Result:

A cross, which radius is equal to the first operand A cross, which radius is equal to the first operand and the width of the lines for the second

Examples:

 
geometry var0 <- cross(10); // var0 equals a geometry as a cross of radius 10 
geometry var1 <- cross(10,2); // var1 equals a geometry as a cross of radius 10, and with a width of 2 for the lines 

`crosses`

Possible use:

geometry crosses geometry ---> bool
crosses (geometry , geometry) ---> bool

Result:

A boolean, equal to true if the left-geometry (or agent/point) crosses the right-geometry (or agent/point).

Special cases:

if one of the operand is null, returns false.
if one operand is a point, returns false.

Examples:

 
bool var0 <- polyline([{10,10},{20,20}]) crosses polyline([{10,20},{20,10}]); // var0 equals true 
bool var1 <- polyline([{10,10},{20,20}]) crosses {15,15}; // var1 equals true 
bool var2 <- polyline([{0,0},{25,25}]) crosses polygon([{10,10},{10,20},{20,20},{20,10}]); // var2 equals true

`crs`

Possible use:

crs (file) ---> string

Result:

the Coordinate Reference System (CRS) of the GIS file

Examples:

 
string var0 <- crs(my_shapefile); // var0 equals the crs of the shapefile

`CRS_transform`

Possible use:

CRS_transform (geometry) ---> geometry
geometry CRS_transform string ---> geometry
CRS_transform (geometry , string) ---> geometry
CRS_transform (geometry, string, string) ---> geometry

Special cases:

returns the geometry corresponding to the transformation of the given geometry by the current CRS (Coordinate Reference System), the one corresponding to the world's agent one

 
geometry var0 <- CRS_transform(shape); // var0 equals a geometry corresponding to the agent geometry transformed into the current CRS

returns the geometry corresponding to the transformation of the given geometry by the left operand CRS (Coordinate Reference System)

 
geometry var1 <- shape CRS_transform("EPSG:4326"); // var1 equals a geometry corresponding to the agent geometry transformed into the EPSG:4326 CRS

returns the geometry corresponding to the transformation of the given geometry from the first CRS to the second CRS (Coordinate Reference System)

 
geometry var2 <- {8.35,47.22} CRS_transform("EPSG:4326","EPSG:4326"); // var2 equals {929517.7481238344,5978057.894895313,0.0}

`csv_file`

Possible use:

csv_file (string) ---> file
string csv_file bool ---> file
csv_file (string , bool) ---> file
string csv_file string ---> file
csv_file (string , string) ---> file
string csv_file matrix<unknown> ---> file
csv_file (string , matrix<unknown>) ---> file
csv_file (string, string, bool) ---> file
csv_file (string, string, any GAML type) ---> file
csv_file (string, string, string, bool) ---> file
csv_file (string, string, string, any GAML type) ---> file
csv_file (string, string, any GAML type, bool) ---> file
csv_file (string, string, any GAML type, point) ---> file

Result:

Constructs a file of type csv. Allowed extensions are limited to csv, tsv

Special cases:

csv_file(string): This file constructor allows to read a CSV file with the default separator (coma), no header, and no assumption on the type of data. No text qualifier will be used

 
csv_file f <- csv_file("file.csv");

csv_file(string,bool): This file constructor allows to read a CSV file with the default separator (coma), with specifying if the model has a header or not (boolean), and no assumption on the type of data. No text qualifier will be used

 
csv_file f <- csv_file("file.csv",true);

csv_file(string,string): This file constructor allows to read a CSV file and specify the separator used, without making any assumption on the type of data. Headers should be detected automatically if they exist. No text qualifier will be used

 
csv_file f <- csv_file("file.csv", ";");

csv_file(string,string,bool): This file constructor allows to read a CSV file and specify (1) the separator used; (2) if the model has a header or not, without making any assumption on the type of data. No text qualifier will be used

 
csv_file f <- csv_file("file.csv", ";",true);

csv_file(string,string,string,bool): This file constructor allows to read a CSV file and specify (1) the separator used; (2) the text qualifier used; (3) if the model has a header or not, without making any assumption on the type of data

 
csv_file f <- csv_file("file.csv", ';', '"', true);

csv_file(string,string,any GAML type): This file constructor allows to read a CSV file with a given separator, no header, and the type of data. No text qualifier will be used

 
csv_file f <- csv_file("file.csv", ";",int);

csv_file(string,string,string,any GAML type): This file constructor allows to read a CSV file and specify the separator, text qualifier to use, and the type of data to read. Headers should be detected automatically if they exist.

 
csv_file f <- csv_file("file.csv", ';', '"', int);

csv_file(string,string,any GAML type,bool): This file constructor allows to read a CSV file with a given separator, the type of data, with specifying if the model has a header or not (boolean). No text qualifier will be used

 
csv_file f <- csv_file("file.csv", ";",int,true);

csv_file(string,string,any GAML type,point): This file constructor allows to read a CSV file with a given separator, the type of data, with specifying the number of cols and rows taken into account. No text qualifier will be used

 
csv_file f <- csv_file("file.csv", ";",int,true, {5, 100});

csv_file(string,matrix<unknown>): This file constructor allows to store a matrix in a CSV file (it does not save it - just store it in memory),

 
csv_file f <- csv_file("file.csv", matrix([10,10],[10,10]));

`cube`

Possible use:

cube (float) ---> geometry

Result:

A cube geometry which side size is equal to the operand.

Comment:

the center of the cube is by default the location of the current agent in which has been called this operator.

Special cases:

returns nil if the operand is nil.

Examples:

 
geometry var0 <- cube(10); // var0 equals a geometry as a square of side size 10.

`curve`

Possible use:

curve (point, point, float) ---> geometry
curve (point, point, point) ---> geometry
curve (point, point, float, float) ---> geometry
curve (point, point, point, int) ---> geometry
curve (point, point, point, point) ---> geometry
curve (point, point, float, bool) ---> geometry
curve (point, point, point, point, int) ---> geometry
curve (point, point, float, int, float) ---> geometry
curve (point, point, float, bool, int) ---> geometry
curve (point, point, float, bool, int, float) ---> geometry
curve (point, point, float, int, float, float) ---> geometry

Result:

A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of the given number of points - the boolean is used to specified if it is the right side and the last value to indicate where is the inflection point (between 0.0 and 1.0 - default 0.5). A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius considering the given rotation angle (90 = along the z axis). A quadratic Bezier curve geometry built from the three given points composed of a given numnber of points. A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of the given number of points, considering the given inflection point (between 0.0 and 1.0 - default 0.5), and the given rotation angle (90 = along the z axis). A cubic Bezier curve geometry built from the four given points composed of 10 points. A cubic Bezier curve geometry built from the four given points composed of a given number of points. A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of the given number of points, considering the given rotation angle (90 = along the z axis). A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of the given number of points - the boolean is used to specified if it is the right side. A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of 10 points. A quadratic Bezier curve geometry built from the three given points composed of 10 points. A cubic Bezier curve geometry built from the two given points with the given coefficient for the radius and composed of 10 points - the last boolean is used to specified if it is the right side.

Special cases:

if the operand is nil, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the last operand (number of points) is inferior to 2, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the last operand (number of points) is inferior to 2, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil
if the operand is nil, returns nil

Examples:

 
geometry var0 <- curve({0,0},{10,10}, 0.5, false, 100, 0.8); // var0 equals a cubic Bezier curve geometry composed of 100 points from p0 to p1 at the right side. 
geometry var1 <- curve({0,0},{10,10}, 0.5, 90); // var1 equals a cubic Bezier curve geometry composed of 100 points from p0 to p1 at the right side. 
geometry var2 <- curve({0,0}, {0,10}, {10,10}, 20); // var2 equals a quadratic Bezier curve geometry composed of 20 points from p0 to p2. 
geometry var3 <- curve({0,0},{10,10}, 0.5, 100, 0.8, 90); // var3 equals a cubic Bezier curve geometry composed of 100 points from p0 to p1 at the right side. 
geometry var4 <- curve({0,0}, {0,10}, {10,10}); // var4 equals a cubic Bezier curve geometry composed of 10 points from p0 to p3. 
geometry var5 <- curve({0,0}, {0,10}, {10,10}); // var5 equals a cubic Bezier curve geometry composed of 10 points from p0 to p3. 
geometry var6 <- curve({0,0},{10,10}, 0.5, 100, 90); // var6 equals a cubic Bezier curve geometry composed of 100 points from p0 to p1 at the right side. 
geometry var7 <- curve({0,0},{10,10}, 0.5, false, 100); // var7 equals a cubic Bezier curve geometry composed of 100 points from p0 to p1 at the right side. 
geometry var8 <- curve({0,0},{10,10}, 0.5); // var8 equals a cubic Bezier curve geometry composed of 10 points from p0 to p1. 
geometry var9 <- curve({0,0}, {0,10}, {10,10}); // var9 equals a quadratic Bezier curve geometry composed of 10 points from p0 to p2. 
geometry var10 <- curve({0,0},{10,10}, 0.5, false); // var10 equals a cubic Bezier curve geometry composed of 10 points from p0 to p1 at the left side.

`cylinder`

Possible use:

float cylinder float ---> geometry
cylinder (float , float) ---> geometry

Result:

A cylinder geometry which radius is equal to the operand.

Comment:

the center of the cylinder is by default the location of the current agent in which has been called this operator.

Special cases:

returns a point if the operand is lower or equal to 0.

Examples:

 
geometry var0 <- cylinder(10,10); // var0 equals a geometry as a circle of radius 10.

Definition​

Priority between operators​

Using actions as operators​

Table of Contents​

Operators by categories​

3D​

Arithmetic operators​

BDI​

Casting operators​

Color-related operators​

Comparison operators​

Containers-related operators​

Date-related operators​

Dates​

Displays​

Driving operators​

edge​

EDP-related operators​

Files-related operators​

FIPA-related operators​

GamaMetaType​

Graphs-related operators​

Grid-related operators​

Iterator operators​

List-related operators​

Logical operators​

Map comparaison operators​

Map-related operators​

Material​

Matrix-related operators​

multicriteria operators​

Path-related operators​

Points-related operators​

Random operators​

ReverseOperators​

Shape​

Spatial operators​

Spatial properties operators​

Spatial queries operators​

Spatial relations operators​

Spatial statistical operators​

Spatial transformations operators​

Species-related operators​

Statistical operators​

Strings-related operators​

SubModel​

System​

Time-related operators​

Types-related operators​

User control operators​

Operators​

BDIPlan​

Possible use:​

Result:​

before​

Possible use:​

Result:​

Examples:​

beta​

Possible use:​

Result:​

Comment:​

Examples:​

beta_index​

Possible use:​

Result:​

Examples:​

See also:​

between​

Possible use:​

Result:​

Special cases:​

Examples:​

betweenness_centrality​

Possible use:​

Result:​

Examples:​

biggest_cliques_of​

Possible use:​

Result:​

Definition

Priority between operators

Using actions as operators

Table of Contents

Operators by categories

3D

Arithmetic operators

BDI

Casting operators

Color-related operators

Comparison operators

Containers-related operators

Date-related operators

Dates

Displays

Driving operators

edge

EDP-related operators

Files-related operators

FIPA-related operators

GamaMetaType

Graphs-related operators

Grid-related operators

Iterator operators

List-related operators

Logical operators

Map comparaison operators

Map-related operators

Material

Matrix-related operators

multicriteria operators

Path-related operators

Points-related operators

Random operators

ReverseOperators

Shape

Spatial operators

Spatial properties operators

Spatial queries operators

Spatial relations operators

Spatial statistical operators

Spatial transformations operators

Species-related operators

Statistical operators

Strings-related operators

SubModel

System

Time-related operators

Types-related operators

User control operators

Operators

`BDIPlan`

Possible use:

Result:

`before`

Possible use:

Result:

Examples:

`beta`

Possible use:

Result:

Comment:

Examples:

`beta_index`

Possible use:

Result:

Examples:

See also:

`between`

Possible use:

Result:

Special cases:

Examples:

`betweenness_centrality`

Possible use:

Result:

Examples:

`biggest_cliques_of`

Possible use:

Result: