Bridge between classical and “modern” derived functors
$begingroup$
This is a question for a reference.
What I would call the classical approach to derived functors, is the following:
Let $F:mathcal{A}to mathcal{B}$ be a right exact functor between abelian categories. When $mathcal{A}$ has enough projectives then we can define a projective resolution $P^bullet$ of any object $A$. We call $H^i(F(P^bullet))$ the derived functors of $F$.
This works mainly because projectives have a bunch of nice properties. For example if $Q^bullet$ is another projective resolution it is not difficult to construct a map between the two and check that we obtain the same results.
The more modern approach uses triangulated categories and localizations to construct $LF:D(mathcal{A})to D(mathcal{B})$. Here it is enough that a family of objects (not necessarily the family of projectives) is sufficiently large. Via $H^i(LF)$ we get much the same results.
However in practice one often uses non-projective resolutions but merely $F$-acyclic resolutions, e.g. flat resolutions in the case of $F=Motimes -$.
My question is if there is a nice source defining derived functors in the 'classical' way, without projectives?
For example it seems natural to me to define $Tor_1(M,N)$ by saying "pick a flat resolution of $N$, apply $Motimes-$ to the resolution and take homology of the resulting complex". But this clearly does not work so nicely, because given two different flat resolutions there is no reason, why there should be a map between them.
reference-request homological-algebra
$endgroup$
add a comment |
$begingroup$
This is a question for a reference.
What I would call the classical approach to derived functors, is the following:
Let $F:mathcal{A}to mathcal{B}$ be a right exact functor between abelian categories. When $mathcal{A}$ has enough projectives then we can define a projective resolution $P^bullet$ of any object $A$. We call $H^i(F(P^bullet))$ the derived functors of $F$.
This works mainly because projectives have a bunch of nice properties. For example if $Q^bullet$ is another projective resolution it is not difficult to construct a map between the two and check that we obtain the same results.
The more modern approach uses triangulated categories and localizations to construct $LF:D(mathcal{A})to D(mathcal{B})$. Here it is enough that a family of objects (not necessarily the family of projectives) is sufficiently large. Via $H^i(LF)$ we get much the same results.
However in practice one often uses non-projective resolutions but merely $F$-acyclic resolutions, e.g. flat resolutions in the case of $F=Motimes -$.
My question is if there is a nice source defining derived functors in the 'classical' way, without projectives?
For example it seems natural to me to define $Tor_1(M,N)$ by saying "pick a flat resolution of $N$, apply $Motimes-$ to the resolution and take homology of the resulting complex". But this clearly does not work so nicely, because given two different flat resolutions there is no reason, why there should be a map between them.
reference-request homological-algebra
$endgroup$
add a comment |
$begingroup$
This is a question for a reference.
What I would call the classical approach to derived functors, is the following:
Let $F:mathcal{A}to mathcal{B}$ be a right exact functor between abelian categories. When $mathcal{A}$ has enough projectives then we can define a projective resolution $P^bullet$ of any object $A$. We call $H^i(F(P^bullet))$ the derived functors of $F$.
This works mainly because projectives have a bunch of nice properties. For example if $Q^bullet$ is another projective resolution it is not difficult to construct a map between the two and check that we obtain the same results.
The more modern approach uses triangulated categories and localizations to construct $LF:D(mathcal{A})to D(mathcal{B})$. Here it is enough that a family of objects (not necessarily the family of projectives) is sufficiently large. Via $H^i(LF)$ we get much the same results.
However in practice one often uses non-projective resolutions but merely $F$-acyclic resolutions, e.g. flat resolutions in the case of $F=Motimes -$.
My question is if there is a nice source defining derived functors in the 'classical' way, without projectives?
For example it seems natural to me to define $Tor_1(M,N)$ by saying "pick a flat resolution of $N$, apply $Motimes-$ to the resolution and take homology of the resulting complex". But this clearly does not work so nicely, because given two different flat resolutions there is no reason, why there should be a map between them.
reference-request homological-algebra
$endgroup$
This is a question for a reference.
What I would call the classical approach to derived functors, is the following:
Let $F:mathcal{A}to mathcal{B}$ be a right exact functor between abelian categories. When $mathcal{A}$ has enough projectives then we can define a projective resolution $P^bullet$ of any object $A$. We call $H^i(F(P^bullet))$ the derived functors of $F$.
This works mainly because projectives have a bunch of nice properties. For example if $Q^bullet$ is another projective resolution it is not difficult to construct a map between the two and check that we obtain the same results.
The more modern approach uses triangulated categories and localizations to construct $LF:D(mathcal{A})to D(mathcal{B})$. Here it is enough that a family of objects (not necessarily the family of projectives) is sufficiently large. Via $H^i(LF)$ we get much the same results.
However in practice one often uses non-projective resolutions but merely $F$-acyclic resolutions, e.g. flat resolutions in the case of $F=Motimes -$.
My question is if there is a nice source defining derived functors in the 'classical' way, without projectives?
For example it seems natural to me to define $Tor_1(M,N)$ by saying "pick a flat resolution of $N$, apply $Motimes-$ to the resolution and take homology of the resulting complex". But this clearly does not work so nicely, because given two different flat resolutions there is no reason, why there should be a map between them.
reference-request homological-algebra
reference-request homological-algebra
asked Jan 15 at 14:32
Rene RecktenwaldRene Recktenwald
1808
1808
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
return StackExchange.using("mathjaxEditing", function () {
StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix) {
StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["$", "$"], ["\\(","\\)"]]);
});
});
}, "mathjax-editing");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "69"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
},
noCode: 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%2fmath.stackexchange.com%2fquestions%2f3074500%2fbridge-between-classical-and-modern-derived-functors%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Mathematics 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.
Use MathJax to format equations. MathJax reference.
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%2fmath.stackexchange.com%2fquestions%2f3074500%2fbridge-between-classical-and-modern-derived-functors%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