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.

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

MNT: http:// → https:// #3097

Merged
merged 2 commits into from
Oct 2, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion Dockerfile
Original file line number Diff line number Diff line change
Expand Up @@ -267,7 +267,7 @@ ARG VERSION
LABEL org.label-schema.build-date=$BUILD_DATE \
org.label-schema.name="fMRIPrep" \
org.label-schema.description="fMRIPrep - robust fMRI preprocessing tool" \
org.label-schema.url="http://fmriprep.org" \
org.label-schema.url="https://fmriprep.org" \
org.label-schema.vcs-ref=$VCS_REF \
org.label-schema.vcs-url="https://github.com/nipreps/fmriprep" \
org.label-schema.version=$VERSION \
Expand Down
2 changes: 1 addition & 1 deletion docs/Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ BUILDDIR = _build

# User-friendly check for sphinx-build
ifeq ($(shell which $(SPHINXBUILD) >/dev/null 2>&1; echo $$?), 1)
$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don\'t have Sphinx installed, grab it from http://sphinx-doc.org/)
$(error The '$(SPHINXBUILD)' command was not found. Make sure you have Sphinx installed, then set the SPHINXBUILD environment variable to point to the full path of the '$(SPHINXBUILD)' executable. Alternatively you can add the directory with the executable to your PATH. If you don\'t have Sphinx installed, grab it from https://www.sphinx-doc.org/)
endif

# Internal variables.
Expand Down
2 changes: 1 addition & 1 deletion docs/installation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -94,6 +94,6 @@ Sherlock enables `the following data transfer options
<https://www.sherlock.stanford.edu/docs/user-guide/storage/data-transfer/>`_.

Alternatively, more comprehensive solutions such as `Datalad
<http://www.datalad.org/>`_ will handle data transfers with the appropriate
<https://www.datalad.org/>`_ will handle data transfers with the appropriate
settings and commands.
Datalad also performs version control over your data.
4 changes: 2 additions & 2 deletions docs/links.rst
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
.. _Nipype: http://nipype.readthedocs.io/en/latest/
.. _BIDS: http://bids.neuroimaging.io
.. _Nipype: https://nipype.readthedocs.io/en/latest/
.. _BIDS: https://bids.neuroimaging.io/
.. _`BIDS Derivatives`: https://bids-specification.readthedocs.io/en/stable/05-derivatives/01-introduction.html
.. _`BEP 011`: https://bids-specification.readthedocs.io/en/bep011/05-derivatives/04-structural-derivatives.html
.. _`BEP 012`: https://bids-specification.readthedocs.io/en/bep012/05-derivatives/05-functional-derivatives.html
Expand Down
8 changes: 4 additions & 4 deletions docs/outputs.rst
Original file line number Diff line number Diff line change
Expand Up @@ -607,7 +607,7 @@ the following invocation::

.. [Behzadi2007] Behzadi Y, Restom K, Liau J, Liu TT, A component-based noise correction method
(CompCor) for BOLD and perfusion-based fMRI. NeuroImage. 2007.
doi:`10.1016/j.neuroimage.2007.04.042 <http://doi.org/10.1016/j.neuroimage.2007.04.042>`_
doi:`10.1016/j.neuroimage.2007.04.042 <https://doi.org/10.1016/j.neuroimage.2007.04.042>`_

.. [Ciric2017] Ciric R, Wolf DH, Power JD, Roalf DR, Baum GL, Ruparel K, Shinohara RT, Elliott MA,
Eickhoff SB, Davatzikos C., Gur RC, Gur RE, Bassett DS, Satterthwaite TD.
Expand All @@ -617,7 +617,7 @@ the following invocation::

.. [Greve2013] Greve DN, Brown GG, Mueller BA, Glover G, Liu TT,
A Survey of the Sources of Noise in fMRI. Psychometrika. 2013.
doi:`10.1007/s11336-013-9344-2 <http://dx.doi.org/10.1007/s11336-013-9344-2>`_
doi:`10.1007/s11336-013-9344-2 <https://doi.org/10.1007/s11336-013-9344-2>`_

.. [Friston1996] Friston KJ1, Williams S, Howard R, Frackowiak RS, Turner R,
Movement‐Related effects in fMRI time‐series. Magnetic Resonance in Medicine. 1996.
Expand All @@ -634,7 +634,7 @@ the following invocation::

.. [Muschelli2014] Muschelli J, Nebel MB, Caffo BS, Barber AD, Pekar JJ, Mostofsky SH,
Reduction of motion-related artifacts in resting state fMRI using aCompCor. NeuroImage. 2014.
doi:`10.1016/j.neuroimage.2014.03.028 <http://doi.org/10.1016/j.neuroimage.2014.03.028>`_
doi:`10.1016/j.neuroimage.2014.03.028 <https://doi.org/10.1016/j.neuroimage.2014.03.028>`_

.. [Parkes2018] Parkes L, Fulcher B, Yücel M, Fornito A, An evaluation of the efficacy, reliability,
and sensitivity of motion correction strategies for resting-state functional MRI. NeuroImage. 2018.
Expand All @@ -653,7 +653,7 @@ the following invocation::
doi:`10.1016/j.neuroimage.2011.10.018 <https://doi.org/10.1016/j.neuroimage.2011.10.018>`_

.. [Power2016] Power JD, A simple but useful way to assess fMRI scan qualities. NeuroImage. 2016.
doi:`10.1016/j.neuroimage.2016.08.009 <http://doi.org/10.1016/j.neuroimage.2016.08.009>`_
doi:`10.1016/j.neuroimage.2016.08.009 <https://doi.org/10.1016/j.neuroimage.2016.08.009>`_

.. [Provins2022] Provins C et al., Quality control and nuisance regression of fMRI, looking out
where signal should not be found. Proc. Intl. Soc. Mag. Reson. Med. 31, London (UK). 2022
Expand Down
4 changes: 2 additions & 2 deletions docs/sphinxext/github_link.py
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,10 @@ def _linkcode_resolve(domain, info, package, url_fmt, revision):
>>> _linkcode_resolve('py', {'module': 'tty',
... 'fullname': 'setraw'},
... package='tty',
... url_fmt='http://hg.python.org/cpython/file/'
... url_fmt='https://hg.python.org/cpython/file/'
... '{revision}/Lib/{package}/{path}#L{lineno}',
... revision='xxxx')
'http://hg.python.org/cpython/file/xxxx/Lib/tty/tty.py#L18'
'https://hg.python.org/cpython/file/xxxx/Lib/tty/tty.py#L18'
"""

if revision is None:
Expand Down
14 changes: 7 additions & 7 deletions docs/usage.rst
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The input dataset is required to be in valid :abbr:`BIDS (Brain Imaging Data
Structure)` format, and it must include at least one T1w structural image and
(unless disabled with a flag) a BOLD series.
We highly recommend that you validate your dataset with the free, online
`BIDS Validator <http://bids-standard.github.io/bids-validator/>`_.
`BIDS Validator <https://bids-standard.github.io/bids-validator/>`_.

The exact command to run *fMRIPRep* depends on the Installation_ method.
The common parts of the command follow the `BIDS-Apps
Expand Down Expand Up @@ -188,27 +188,27 @@ Because processing this emerging type of datasets (*densely sampled neuroimaging

Troubleshooting
---------------
Logs and crashfiles are outputted into the
Logs and crashfiles are output into the
``<output dir>/fmriprep/sub-<participant_label>/log`` directory.
Information on how to customize and understand these files can be found on the
`nipype debugging <http://nipype.readthedocs.io/en/latest/users/debug.html>`_
`Debugging Nipype Workflows <http://nipype.readthedocs.io/en/latest/users/debug.html>`_
page.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This page has disappeared from recent documentation. Not sure an equivalent page is available, I have therefore discarded the whole sentence.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.


**Support and communication**.
The documentation of this project is found here: http://fmriprep.readthedocs.org/en/latest/.
The documentation of this project is found here: https://fmriprep.readthedocs.org/en/latest/.

All bugs, concerns and enhancement requests for this software can be submitted here:
https://github.com/nipreps/fmriprep/issues.

If you have a problem or would like to ask a question about how to use *fMRIPRep*,
please submit a question to `NeuroStars.org <http://neurostars.org/tags/fmriprep>`_ with an ``fmriprep`` tag.
please submit a question to `NeuroStars.org <https://neurostars.org/tag/fmriprep>`_ with an ``fmriprep`` tag.
NeuroStars.org is a platform similar to StackOverflow but dedicated to neuroinformatics.

Previous questions about *fMRIPRep* are available here:
http://neurostars.org/tags/fmriprep/
https://neurostars.org/tag/fmriprep/

To participate in the *fMRIPRep* development-related discussions please use the
following mailing list: http://mail.python.org/mailman/listinfo/neuroimaging
following mailing list: https://mail.python.org/mailman/listinfo/neuroimaging
Please add *[fmriprep]* to the subject line when posting on the mailing list.


Expand Down
Loading