Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make dynamic map range docs more explicit #1474

Merged
merged 1 commit into from
Dec 11, 2023
Merged

Make dynamic map range docs more explicit #1474

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/sdfg/ir.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -481,8 +481,8 @@ current entry node, use the :func:`~dace.sdfg.state.StateGraphView.exit_node` me

**Dynamic Map Ranges**: Such ranges can use memlets to define the map ranges directly from data containers, while
still retaining the dataflow of a single state. As they are fed into a view connector on the map entry node, their value
(described by the connector name) can be used in the symbolic expressions of the map range. Only scalar connectors are
allowed.
(described by the connector name) can be used in the symbolic expressions of the map range, and anywhere inside the map
scope as a symbol (same as the iteration variables). Only scalar connectors are allowed.

In the following example, we use dynamic map ranges to compute a sparse matrix-vector multiplication,
where the vector is dense. Every output row has a defined range (standard, symbolic map), whereas the corresponding rows
Expand Down
Loading