1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
use ;
/// A unique identifier for a tensor index.
///
/// Tensor indices are identified in two distinct locations by this type alias:
///
/// 1) Local Tensor indices: `TensorExpression` objects generate tensor data
/// in a specific order. The ordering of their local tensor indices is identified
/// by their local index ids. These do not change unless the `TensorExpression`'s
/// internal symbolic expression changes. Therefore, it is important to track
/// it's local tensor index ordering, so we can accurately perform contractions
/// dictated by the network. See `[TensorIndex]` for more information.
///
/// 2) Global Tensor Network indices: The entire network will have a list of
/// indices and each will have its own id. See `[NetworkIndex]` for more
/// information.
pub type IndexId = usize;
/// Represents the size or dimension of an index in a tensor network.
///
/// This type alias is used to specify the number of possible values for an index.
/// From a quantum circuit perspective, Input and Output indices usually have
/// size equal to radix of the qudit captured by the leg (2 for qubits, 3 for
/// qutrits, etc); however, during contraction simplification, many edges can
/// be grouped together to simplify the number of contractions, leading to a
/// larger index size.
pub type IndexSize = usize;
/// Represents a weighted-indexed edge in a tensor network.
///
/// This provides the core index information for contraction ordering solvers.
pub type WeightedIndex = ;
/// IndexDirection represents a tensor's leg direction from the quantum circuit perspective.
///
/// In the context of quantum circuits and tensor networks, indices (or "legs") of a tensor
/// are categorized by their direction to signify their role in an operation.
///
/// While tensors may conceptually have multiple indices (legs), in the `qudit-expr` library,
/// `TensorExpression` objects are always generated as 1-D, 2-D, or 3-D tensors. This enum
/// links the conceptual/graphical tensor indices to the generated expression's dimensions by grouping
/// them along directions. So all `Input`, `Output`, and `Batch` legs correspond to a
/// specific dimension of the generated tensor. This tensor network library can
/// use this to predict and manipulate the shape of a generated tensor.
///
/// For example, kets capture quantum states, and are represented conceptually
/// by column vectors. In the tensor network perspective, they are represented by
/// a tensor with only `Output` indices. They have as many indices as there are
/// qudits in the state and the size of each index is the radix of the qudit.
/// For qubits, the radix is 2, so all indices would have dimension 2. However,
/// when generated in the `qudit-expr` library, they are generated as a vector.
/// The `IndexDirection` is what is used by the `qudit-tensor` library to expect
/// a vector shape, since a ket tensor will only have indices in one direction.
///
/// Similarly, gates which capture quantum operations, are represented by unitary
/// matrices. As a tensor, they have indices that point in both `Input` and `Output`
/// directions. Even though there will likely be more than 2 indices, the `qudit-tensor`
/// library expects a matrix to be generated by the underlying `TensorExpression`
/// because of the two distinct directions.
///
/// Batch indices are used for measurements/Kraus operators or for batch executions
/// of a network.
/// Represents an index of a tensor.
///
/// Indices in this format are associated with a direction, and as a result,
/// an expected output or expected generation (input) shape and ordering.
/// For example, a `[super::network::QuditTensorNetwork]` will store its output
/// indices in this format because after evaluation, there will
/// be an expected shape and ordering. The shape is determined by all the
/// indices directions and sizes, and the ordering will be determined by the ids.
///
/// # See Also
///
/// - `[super::tensor::QuditTensor]` - Tensor object capturing how tensors are generated.
/// - `[super::network::QuditTensorNetwork]` - Tensor network describing a desired calculation.