Multiline equation with some characters that span all lines
I'm attempting to create a multiline equation with some characters than span both lines.
I've come closer by using the amsmath package
begin{multline*}
Pr[Xleftarrow DECODE(Delta;r_1,...,r_ell) |
displaystyle{(Delta;q_1,...,q_ell)leftarrow QUERY(1^lambda;J)} \
displaystyle{Lambda (Lambda^ell _{j=1})}
]
end{multline*}
But I'm at a loss as this does not allow me to span some characters on both lines
Any suggestions would be appreciated.
equations amsmath
add a comment |
I'm attempting to create a multiline equation with some characters than span both lines.
I've come closer by using the amsmath package
begin{multline*}
Pr[Xleftarrow DECODE(Delta;r_1,...,r_ell) |
displaystyle{(Delta;q_1,...,q_ell)leftarrow QUERY(1^lambda;J)} \
displaystyle{Lambda (Lambda^ell _{j=1})}
]
end{multline*}
But I'm at a loss as this does not allow me to span some characters on both lines
Any suggestions would be appreciated.
equations amsmath
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
Please tell us a bit more whatLambda
stands for? E.g., is is an "operator", likesum
,prod
, orint
?
– Mico
Dec 16 at 20:19
add a comment |
I'm attempting to create a multiline equation with some characters than span both lines.
I've come closer by using the amsmath package
begin{multline*}
Pr[Xleftarrow DECODE(Delta;r_1,...,r_ell) |
displaystyle{(Delta;q_1,...,q_ell)leftarrow QUERY(1^lambda;J)} \
displaystyle{Lambda (Lambda^ell _{j=1})}
]
end{multline*}
But I'm at a loss as this does not allow me to span some characters on both lines
Any suggestions would be appreciated.
equations amsmath
I'm attempting to create a multiline equation with some characters than span both lines.
I've come closer by using the amsmath package
begin{multline*}
Pr[Xleftarrow DECODE(Delta;r_1,...,r_ell) |
displaystyle{(Delta;q_1,...,q_ell)leftarrow QUERY(1^lambda;J)} \
displaystyle{Lambda (Lambda^ell _{j=1})}
]
end{multline*}
But I'm at a loss as this does not allow me to span some characters on both lines
Any suggestions would be appreciated.
equations amsmath
equations amsmath
edited Dec 16 at 15:47
Mico
273k30369756
273k30369756
asked Dec 16 at 15:12
Tarald Riise
311
311
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
Please tell us a bit more whatLambda
stands for? E.g., is is an "operator", likesum
,prod
, orint
?
– Mico
Dec 16 at 20:19
add a comment |
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
Please tell us a bit more whatLambda
stands for? E.g., is is an "operator", likesum
,prod
, orint
?
– Mico
Dec 16 at 20:19
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
Please tell us a bit more what
Lambda
stands for? E.g., is is an "operator", like sum
, prod
, or int
?– Mico
Dec 16 at 20:19
Please tell us a bit more what
Lambda
stands for? E.g., is is an "operator", like sum
, prod
, or int
?– Mico
Dec 16 at 20:19
add a comment |
3 Answers
3
active
oldest
votes
My main suggestions are (a) use biggl[
, biggm|
, and biggr]
to structure the equation and (b) use a two-row array
environment for the material between biggm|
and biggr]
. I wouldn't use a multline*
environment, though. An unnumbered single-line display math environment does fine.
documentclass{article}
usepackage{amsmath}
usepackage{array} % for 'newcolumntype' macro
newcolumntype{L}{>{displaystyle}l} % automatic displaystyle math mode
begin{document}
[
Prbiggl[
Xleftarrow mathit{DECODE}(Delta;r_1,dots,r_ell)
biggm|
begin{array}{@{}L@{}}
(Delta;q_1,dots,q_ell)leftarrow mathit{QUERY}(1^lambda;J) \
Lambda bigl(Lambda^ell_{j=1}leftarrow mathit{RESPOND}(X^{(j)};q_j)bigr)
end{array}
biggr]
]
end{document}
add a comment |
The image has several inconsistencies in the typesetting.
I suggest to define semantic commands in order to be sure that similar objects are always typeset the same.
I don't like ell
, but you can use it in place of the plain l
.
documentclass{article}
usepackage{amsmath}
newcommand{func}[1]{mathit{#1}}
begin{document}
begin{equation*}
Prleft[
X gets func{DECODE}(Delta;r_1,dots,r_l)
;middle|;
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
right]
end{equation*}
end{document}
A slightly different approach, where you specify the brackets as inherently attached to Pr
and can choose their size (see the documentation of DeclarePairedDelimiter
in mathtools
). Basically, Pr*
selects automatic size, Pr[big]
(or any other delimiter size changing command in the optional argument) selects the stated size.
documentclass{article}
usepackage{amsmath,mathtools}
newcommand{func}[1]{mathit{#1}}
renewcommand{Pr}{operatorname{Pr}brackets}
DeclarePairedDelimiterX{brackets}[1]{[}{]}{#1}
newcommand{given}{;delimsize|;mathopen{}}
begin{document}
begin{equation*}
Pr*{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[Big]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[bigg]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
end{document}
add a comment |
by use of array
:
documentclass{article}
usepackage{amsmath}
begin{document}
[
Pr left[Xleftarrowtext{DECODE}(Delta;r_1,dotsc,r_ell) middle|
begin{array}{l}
(Delta;q_1,dotsc,q_ell)leftarrow text{QUERY}(1^lambda;J) \
Lambda(Lambda^ell _{j=1}) leftarrowtext{RESPOND}(X^{(j)}:q_j)
end{array}
right]
]
end{document}
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
Also, missingdots
.
– Sigur
Dec 16 at 15:27
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing)
afterq_j
. :-)
– Sigur
Dec 17 at 10:39
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f466089%2fmultiline-equation-with-some-characters-that-span-all-lines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
My main suggestions are (a) use biggl[
, biggm|
, and biggr]
to structure the equation and (b) use a two-row array
environment for the material between biggm|
and biggr]
. I wouldn't use a multline*
environment, though. An unnumbered single-line display math environment does fine.
documentclass{article}
usepackage{amsmath}
usepackage{array} % for 'newcolumntype' macro
newcolumntype{L}{>{displaystyle}l} % automatic displaystyle math mode
begin{document}
[
Prbiggl[
Xleftarrow mathit{DECODE}(Delta;r_1,dots,r_ell)
biggm|
begin{array}{@{}L@{}}
(Delta;q_1,dots,q_ell)leftarrow mathit{QUERY}(1^lambda;J) \
Lambda bigl(Lambda^ell_{j=1}leftarrow mathit{RESPOND}(X^{(j)};q_j)bigr)
end{array}
biggr]
]
end{document}
add a comment |
My main suggestions are (a) use biggl[
, biggm|
, and biggr]
to structure the equation and (b) use a two-row array
environment for the material between biggm|
and biggr]
. I wouldn't use a multline*
environment, though. An unnumbered single-line display math environment does fine.
documentclass{article}
usepackage{amsmath}
usepackage{array} % for 'newcolumntype' macro
newcolumntype{L}{>{displaystyle}l} % automatic displaystyle math mode
begin{document}
[
Prbiggl[
Xleftarrow mathit{DECODE}(Delta;r_1,dots,r_ell)
biggm|
begin{array}{@{}L@{}}
(Delta;q_1,dots,q_ell)leftarrow mathit{QUERY}(1^lambda;J) \
Lambda bigl(Lambda^ell_{j=1}leftarrow mathit{RESPOND}(X^{(j)};q_j)bigr)
end{array}
biggr]
]
end{document}
add a comment |
My main suggestions are (a) use biggl[
, biggm|
, and biggr]
to structure the equation and (b) use a two-row array
environment for the material between biggm|
and biggr]
. I wouldn't use a multline*
environment, though. An unnumbered single-line display math environment does fine.
documentclass{article}
usepackage{amsmath}
usepackage{array} % for 'newcolumntype' macro
newcolumntype{L}{>{displaystyle}l} % automatic displaystyle math mode
begin{document}
[
Prbiggl[
Xleftarrow mathit{DECODE}(Delta;r_1,dots,r_ell)
biggm|
begin{array}{@{}L@{}}
(Delta;q_1,dots,q_ell)leftarrow mathit{QUERY}(1^lambda;J) \
Lambda bigl(Lambda^ell_{j=1}leftarrow mathit{RESPOND}(X^{(j)};q_j)bigr)
end{array}
biggr]
]
end{document}
My main suggestions are (a) use biggl[
, biggm|
, and biggr]
to structure the equation and (b) use a two-row array
environment for the material between biggm|
and biggr]
. I wouldn't use a multline*
environment, though. An unnumbered single-line display math environment does fine.
documentclass{article}
usepackage{amsmath}
usepackage{array} % for 'newcolumntype' macro
newcolumntype{L}{>{displaystyle}l} % automatic displaystyle math mode
begin{document}
[
Prbiggl[
Xleftarrow mathit{DECODE}(Delta;r_1,dots,r_ell)
biggm|
begin{array}{@{}L@{}}
(Delta;q_1,dots,q_ell)leftarrow mathit{QUERY}(1^lambda;J) \
Lambda bigl(Lambda^ell_{j=1}leftarrow mathit{RESPOND}(X^{(j)};q_j)bigr)
end{array}
biggr]
]
end{document}
edited Dec 16 at 15:46
answered Dec 16 at 15:28
Mico
273k30369756
273k30369756
add a comment |
add a comment |
The image has several inconsistencies in the typesetting.
I suggest to define semantic commands in order to be sure that similar objects are always typeset the same.
I don't like ell
, but you can use it in place of the plain l
.
documentclass{article}
usepackage{amsmath}
newcommand{func}[1]{mathit{#1}}
begin{document}
begin{equation*}
Prleft[
X gets func{DECODE}(Delta;r_1,dots,r_l)
;middle|;
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
right]
end{equation*}
end{document}
A slightly different approach, where you specify the brackets as inherently attached to Pr
and can choose their size (see the documentation of DeclarePairedDelimiter
in mathtools
). Basically, Pr*
selects automatic size, Pr[big]
(or any other delimiter size changing command in the optional argument) selects the stated size.
documentclass{article}
usepackage{amsmath,mathtools}
newcommand{func}[1]{mathit{#1}}
renewcommand{Pr}{operatorname{Pr}brackets}
DeclarePairedDelimiterX{brackets}[1]{[}{]}{#1}
newcommand{given}{;delimsize|;mathopen{}}
begin{document}
begin{equation*}
Pr*{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[Big]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[bigg]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
end{document}
add a comment |
The image has several inconsistencies in the typesetting.
I suggest to define semantic commands in order to be sure that similar objects are always typeset the same.
I don't like ell
, but you can use it in place of the plain l
.
documentclass{article}
usepackage{amsmath}
newcommand{func}[1]{mathit{#1}}
begin{document}
begin{equation*}
Prleft[
X gets func{DECODE}(Delta;r_1,dots,r_l)
;middle|;
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
right]
end{equation*}
end{document}
A slightly different approach, where you specify the brackets as inherently attached to Pr
and can choose their size (see the documentation of DeclarePairedDelimiter
in mathtools
). Basically, Pr*
selects automatic size, Pr[big]
(or any other delimiter size changing command in the optional argument) selects the stated size.
documentclass{article}
usepackage{amsmath,mathtools}
newcommand{func}[1]{mathit{#1}}
renewcommand{Pr}{operatorname{Pr}brackets}
DeclarePairedDelimiterX{brackets}[1]{[}{]}{#1}
newcommand{given}{;delimsize|;mathopen{}}
begin{document}
begin{equation*}
Pr*{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[Big]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[bigg]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
end{document}
add a comment |
The image has several inconsistencies in the typesetting.
I suggest to define semantic commands in order to be sure that similar objects are always typeset the same.
I don't like ell
, but you can use it in place of the plain l
.
documentclass{article}
usepackage{amsmath}
newcommand{func}[1]{mathit{#1}}
begin{document}
begin{equation*}
Prleft[
X gets func{DECODE}(Delta;r_1,dots,r_l)
;middle|;
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
right]
end{equation*}
end{document}
A slightly different approach, where you specify the brackets as inherently attached to Pr
and can choose their size (see the documentation of DeclarePairedDelimiter
in mathtools
). Basically, Pr*
selects automatic size, Pr[big]
(or any other delimiter size changing command in the optional argument) selects the stated size.
documentclass{article}
usepackage{amsmath,mathtools}
newcommand{func}[1]{mathit{#1}}
renewcommand{Pr}{operatorname{Pr}brackets}
DeclarePairedDelimiterX{brackets}[1]{[}{]}{#1}
newcommand{given}{;delimsize|;mathopen{}}
begin{document}
begin{equation*}
Pr*{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[Big]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[bigg]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
end{document}
The image has several inconsistencies in the typesetting.
I suggest to define semantic commands in order to be sure that similar objects are always typeset the same.
I don't like ell
, but you can use it in place of the plain l
.
documentclass{article}
usepackage{amsmath}
newcommand{func}[1]{mathit{#1}}
begin{document}
begin{equation*}
Prleft[
X gets func{DECODE}(Delta;r_1,dots,r_l)
;middle|;
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
right]
end{equation*}
end{document}
A slightly different approach, where you specify the brackets as inherently attached to Pr
and can choose their size (see the documentation of DeclarePairedDelimiter
in mathtools
). Basically, Pr*
selects automatic size, Pr[big]
(or any other delimiter size changing command in the optional argument) selects the stated size.
documentclass{article}
usepackage{amsmath,mathtools}
newcommand{func}[1]{mathit{#1}}
renewcommand{Pr}{operatorname{Pr}brackets}
DeclarePairedDelimiterX{brackets}[1]{[}{]}{#1}
newcommand{given}{;delimsize|;mathopen{}}
begin{document}
begin{equation*}
Pr*{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[Big]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
begin{equation*}
Pr[bigg]{
X gets func{DECODE}(Delta;r_1,dots,r_l)
given
begin{matrix}
(Delta;q_1,dots,q_l) gets func{QUERY}(1^lambda;J) \
Lambda(Lambda_{j=1}^l gets func{RESPOND}(X^{(j)};q_j))
end{matrix}
}
end{equation*}
end{document}
answered Dec 16 at 15:51
egreg
708k8618813163
708k8618813163
add a comment |
add a comment |
by use of array
:
documentclass{article}
usepackage{amsmath}
begin{document}
[
Pr left[Xleftarrowtext{DECODE}(Delta;r_1,dotsc,r_ell) middle|
begin{array}{l}
(Delta;q_1,dotsc,q_ell)leftarrow text{QUERY}(1^lambda;J) \
Lambda(Lambda^ell _{j=1}) leftarrowtext{RESPOND}(X^{(j)}:q_j)
end{array}
right]
]
end{document}
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
Also, missingdots
.
– Sigur
Dec 16 at 15:27
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing)
afterq_j
. :-)
– Sigur
Dec 17 at 10:39
add a comment |
by use of array
:
documentclass{article}
usepackage{amsmath}
begin{document}
[
Pr left[Xleftarrowtext{DECODE}(Delta;r_1,dotsc,r_ell) middle|
begin{array}{l}
(Delta;q_1,dotsc,q_ell)leftarrow text{QUERY}(1^lambda;J) \
Lambda(Lambda^ell _{j=1}) leftarrowtext{RESPOND}(X^{(j)}:q_j)
end{array}
right]
]
end{document}
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
Also, missingdots
.
– Sigur
Dec 16 at 15:27
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing)
afterq_j
. :-)
– Sigur
Dec 17 at 10:39
add a comment |
by use of array
:
documentclass{article}
usepackage{amsmath}
begin{document}
[
Pr left[Xleftarrowtext{DECODE}(Delta;r_1,dotsc,r_ell) middle|
begin{array}{l}
(Delta;q_1,dotsc,q_ell)leftarrow text{QUERY}(1^lambda;J) \
Lambda(Lambda^ell _{j=1}) leftarrowtext{RESPOND}(X^{(j)}:q_j)
end{array}
right]
]
end{document}
by use of array
:
documentclass{article}
usepackage{amsmath}
begin{document}
[
Pr left[Xleftarrowtext{DECODE}(Delta;r_1,dotsc,r_ell) middle|
begin{array}{l}
(Delta;q_1,dotsc,q_ell)leftarrow text{QUERY}(1^lambda;J) \
Lambda(Lambda^ell _{j=1}) leftarrowtext{RESPOND}(X^{(j)}:q_j)
end{array}
right]
]
end{document}
edited Dec 17 at 11:29
answered Dec 16 at 15:23
Zarko
120k865156
120k865156
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
Also, missingdots
.
– Sigur
Dec 16 at 15:27
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing)
afterq_j
. :-)
– Sigur
Dec 17 at 10:39
add a comment |
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
Also, missingdots
.
– Sigur
Dec 16 at 15:27
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing)
afterq_j
. :-)
– Sigur
Dec 17 at 10:39
1
1
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
You won by few seconds. lol
– Sigur
Dec 16 at 15:27
1
1
Also, missing
dots
.– Sigur
Dec 16 at 15:27
Also, missing
dots
.– Sigur
Dec 16 at 15:27
1
1
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
thank you very much to all who pointed me to weakness/errors in my code. i was to much focused to show solution how to write right part of expression in two left aligned lines.
– Zarko
Dec 16 at 15:42
It is missing
)
after q_j
. :-)– Sigur
Dec 17 at 10:39
It is missing
)
after q_j
. :-)– Sigur
Dec 17 at 10:39
add a comment |
Thanks for contributing an answer to TeX - LaTeX Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f466089%2fmultiline-equation-with-some-characters-that-span-all-lines%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What about insert the right contents in array with 2 rows?
– Sigur
Dec 16 at 15:19
Please tell us a bit more what
Lambda
stands for? E.g., is is an "operator", likesum
,prod
, orint
?– Mico
Dec 16 at 20:19