We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
The example transp3.mod + transp3.dat from the AMPL book has the following definitions:
set ORIG; set DEST; set LINKS within {ORIG,DEST}; var Trans {LINKS} >= 0;
The data for LINKS is a subset of the origin-destination pairs. A 2D spreadsheet table of the Trans variables can be specified equivalently as
LINKS
Trans
table Transp3 OUT "amplxl" "2D" "Transp3.xlsx": {(i,j) in LINKS} -> [ORIG,DEST], Trans[i,j];
or
table Transp3 OUT "amplxl" "2D" "Transp3.xlsx": [ORIG,DEST], Trans;
But write table Transp3; fails with this error:
write table Transp3;
Error writing table Transp3 with table handler amplxl: Could not write 2D data
When "2D" is removed from either table statement, the corresponding 1D table is written correctly.
"2D"
The text was updated successfully, but these errors were encountered:
Fixed in e1e3342. Published in https://github.com/ampl/tables/tree/0.1.5.
Sorry, something went wrong.
No branches or pull requests
The example transp3.mod + transp3.dat from the AMPL book has the following definitions:
The data for
LINKS
is a subset of the origin-destination pairs. A 2D spreadsheet table of theTrans
variables can be specified equivalently asor
But
write table Transp3;
fails with this error:When
"2D"
is removed from either table statement, the corresponding 1D table is written correctly.The text was updated successfully, but these errors were encountered: