siunitx: some options must be in preamble, not with S[?
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
This is my question for siunitx users: Is it necessary to specify the input-symbols parameter in the preamble, rather than within S?
Why do I ask?
Here's a table produced by my R function outreg in the package rockchalk.
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false]@
hline
& multicolumn1cWhichever& multicolumn1cWhatevertabularnewline
& multicolumn1cEstimate& multicolumn1cEstimatetabularnewline
& multicolumn1c(S.E.)& multicolumn1c(S.E.)tabularnewline
hline
hline
(Intercept) &403.245*** &29.774*** tabularnewline
& (0.618) & (0.522)tabularnewline
x1 &1.546*& multicolumn1cphantom000. tabularnewline
& (0.692) & tabularnewline
x2 & multicolumn1cphantom000. &3.413** tabularnewline
& & (0.512)tabularnewline
hline
N& multicolumn1c100& multicolumn1c100 tabularnewline
RMSE &6.121 &5.205 tabularnewline
$R^2$ &0.048 &0.312 tabularnewline
adj $R^2$ &0.039 &0.305 tabularnewline
AIC &617.694 &617.694tabularnewline
hline
hline
multicolumn3l$* ple 0.05$$*!!* ple 0.01$$*!!*!!* ple 0.001$tabularnewline
endtabular
endtable
enddocument
Thanks to the help of members in this group, the output is mostly adequate, IMHO. I cannot know ahead of time how many digits might be used, so I don't rely on table-format to tighten down the alignment. That's why I've got the nagging problems about centering of different sections of table. But this is, honestly, much better than I had before.
I'm asking now about the preamble and sisetup. I want the table markup to be as close to portable as possible, not depending on any preamble details.
I wanted to eliminate entirely the use of sisetup, but if I remove that from this example, it does not compile because the parentheses are not understandable to the compiler:
! siunitx error: "invalid-number"
!
! Invalid numerical input '(0.618)'.
!
! See the siunitx documentation for further information.
Is the preamble sisetup the only correction?
siunitx
add a comment |Â
up vote
3
down vote
favorite
This is my question for siunitx users: Is it necessary to specify the input-symbols parameter in the preamble, rather than within S?
Why do I ask?
Here's a table produced by my R function outreg in the package rockchalk.
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false]@
hline
& multicolumn1cWhichever& multicolumn1cWhatevertabularnewline
& multicolumn1cEstimate& multicolumn1cEstimatetabularnewline
& multicolumn1c(S.E.)& multicolumn1c(S.E.)tabularnewline
hline
hline
(Intercept) &403.245*** &29.774*** tabularnewline
& (0.618) & (0.522)tabularnewline
x1 &1.546*& multicolumn1cphantom000. tabularnewline
& (0.692) & tabularnewline
x2 & multicolumn1cphantom000. &3.413** tabularnewline
& & (0.512)tabularnewline
hline
N& multicolumn1c100& multicolumn1c100 tabularnewline
RMSE &6.121 &5.205 tabularnewline
$R^2$ &0.048 &0.312 tabularnewline
adj $R^2$ &0.039 &0.305 tabularnewline
AIC &617.694 &617.694tabularnewline
hline
hline
multicolumn3l$* ple 0.05$$*!!* ple 0.01$$*!!*!!* ple 0.001$tabularnewline
endtabular
endtable
enddocument
Thanks to the help of members in this group, the output is mostly adequate, IMHO. I cannot know ahead of time how many digits might be used, so I don't rely on table-format to tighten down the alignment. That's why I've got the nagging problems about centering of different sections of table. But this is, honestly, much better than I had before.
I'm asking now about the preamble and sisetup. I want the table markup to be as close to portable as possible, not depending on any preamble details.
I wanted to eliminate entirely the use of sisetup, but if I remove that from this example, it does not compile because the parentheses are not understandable to the compiler:
! siunitx error: "invalid-number"
!
! Invalid numerical input '(0.618)'.
!
! See the siunitx documentation for further information.
Is the preamble sisetup the only correction?
siunitx
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
This is my question for siunitx users: Is it necessary to specify the input-symbols parameter in the preamble, rather than within S?
Why do I ask?
Here's a table produced by my R function outreg in the package rockchalk.
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false]@
hline
& multicolumn1cWhichever& multicolumn1cWhatevertabularnewline
& multicolumn1cEstimate& multicolumn1cEstimatetabularnewline
& multicolumn1c(S.E.)& multicolumn1c(S.E.)tabularnewline
hline
hline
(Intercept) &403.245*** &29.774*** tabularnewline
& (0.618) & (0.522)tabularnewline
x1 &1.546*& multicolumn1cphantom000. tabularnewline
& (0.692) & tabularnewline
x2 & multicolumn1cphantom000. &3.413** tabularnewline
& & (0.512)tabularnewline
hline
N& multicolumn1c100& multicolumn1c100 tabularnewline
RMSE &6.121 &5.205 tabularnewline
$R^2$ &0.048 &0.312 tabularnewline
adj $R^2$ &0.039 &0.305 tabularnewline
AIC &617.694 &617.694tabularnewline
hline
hline
multicolumn3l$* ple 0.05$$*!!* ple 0.01$$*!!*!!* ple 0.001$tabularnewline
endtabular
endtable
enddocument
Thanks to the help of members in this group, the output is mostly adequate, IMHO. I cannot know ahead of time how many digits might be used, so I don't rely on table-format to tighten down the alignment. That's why I've got the nagging problems about centering of different sections of table. But this is, honestly, much better than I had before.
I'm asking now about the preamble and sisetup. I want the table markup to be as close to portable as possible, not depending on any preamble details.
I wanted to eliminate entirely the use of sisetup, but if I remove that from this example, it does not compile because the parentheses are not understandable to the compiler:
! siunitx error: "invalid-number"
!
! Invalid numerical input '(0.618)'.
!
! See the siunitx documentation for further information.
Is the preamble sisetup the only correction?
siunitx
This is my question for siunitx users: Is it necessary to specify the input-symbols parameter in the preamble, rather than within S?
Why do I ask?
Here's a table produced by my R function outreg in the package rockchalk.
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false]@
hline
& multicolumn1cWhichever& multicolumn1cWhatevertabularnewline
& multicolumn1cEstimate& multicolumn1cEstimatetabularnewline
& multicolumn1c(S.E.)& multicolumn1c(S.E.)tabularnewline
hline
hline
(Intercept) &403.245*** &29.774*** tabularnewline
& (0.618) & (0.522)tabularnewline
x1 &1.546*& multicolumn1cphantom000. tabularnewline
& (0.692) & tabularnewline
x2 & multicolumn1cphantom000. &3.413** tabularnewline
& & (0.512)tabularnewline
hline
N& multicolumn1c100& multicolumn1c100 tabularnewline
RMSE &6.121 &5.205 tabularnewline
$R^2$ &0.048 &0.312 tabularnewline
adj $R^2$ &0.039 &0.305 tabularnewline
AIC &617.694 &617.694tabularnewline
hline
hline
multicolumn3l$* ple 0.05$$*!!* ple 0.01$$*!!*!!* ple 0.001$tabularnewline
endtabular
endtable
enddocument
Thanks to the help of members in this group, the output is mostly adequate, IMHO. I cannot know ahead of time how many digits might be used, so I don't rely on table-format to tighten down the alignment. That's why I've got the nagging problems about centering of different sections of table. But this is, honestly, much better than I had before.
I'm asking now about the preamble and sisetup. I want the table markup to be as close to portable as possible, not depending on any preamble details.
I wanted to eliminate entirely the use of sisetup, but if I remove that from this example, it does not compile because the parentheses are not understandable to the compiler:
! siunitx error: "invalid-number"
!
! Invalid numerical input '(0.618)'.
!
! See the siunitx documentation for further information.
Is the preamble sisetup the only correction?
siunitx
siunitx
asked 2 hours ago
pauljohn32
334110
334110
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
6
down vote
accepted
Your syntax of the tabular preamble is faulty. You are using *2S[...]
But you should put braces around the second argument so that the optional argument of S is processed too:
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
% input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[
input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false
]@
& (0.618) & (0.522)tabularnewline
endtabular
endtable
enddocument
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
6
down vote
accepted
Your syntax of the tabular preamble is faulty. You are using *2S[...]
But you should put braces around the second argument so that the optional argument of S is processed too:
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
% input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[
input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false
]@
& (0.618) & (0.522)tabularnewline
endtabular
endtable
enddocument
add a comment |Â
up vote
6
down vote
accepted
Your syntax of the tabular preamble is faulty. You are using *2S[...]
But you should put braces around the second argument so that the optional argument of S is processed too:
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
% input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[
input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false
]@
& (0.618) & (0.522)tabularnewline
endtabular
endtable
enddocument
add a comment |Â
up vote
6
down vote
accepted
up vote
6
down vote
accepted
Your syntax of the tabular preamble is faulty. You are using *2S[...]
But you should put braces around the second argument so that the optional argument of S is processed too:
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
% input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[
input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false
]@
& (0.618) & (0.522)tabularnewline
endtabular
endtable
enddocument
Your syntax of the tabular preamble is faulty. You are using *2S[...]
But you should put braces around the second argument so that the optional argument of S is processed too:
documentclass[11pt,letterpaper,english]extarticle
usepackagebooktabs
usepackagedcolumn
usepackagearray
usepackagesiunitx
%following now in each table
sisetup
% input-symbols = ( )
begindocument
begintable
captionStill have showAIC argument, as in previous versionslabeltab:ex5ds
centeringbegintabular@l*2S[
input-symbols = ( ),
group-digits = false,
table-format = 3.3,
table-number-alignment = center,
table-space-text-pre = (,
table-space-text-post = ***,
table-align-text-pre = false,
table-align-text-post = false,
parse-units = false
]@
& (0.618) & (0.522)tabularnewline
endtabular
endtable
enddocument
answered 44 mins ago
Ulrike Fischer
180k7285655
180k7285655
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f454785%2fsiunitx-some-options-must-be-in-preamble-not-with-s%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password