Do we expect the following syntax to work?

julia> [Int, Float64, String, Bool] .<: Union{Int, String}
ERROR: syntax: space not allowed after ":" used for quoting

It works if you call <: as a broadcasted function:

julia> (<:).([Int, Float64, String, Bool], Union{Int, String})
4-element BitArray{1}:
 1
 0
 1
 0

Version info:

Julia Versio

Checklist

Please ensure the following tasks are completed before filing a bug report.

• Read and understood the [Code of Conduct][code-of-conduct].
• Searched for existing issues and pull requests.

Description

Description of the issue.

The following code produces an array whose shape does not match what I'd expect:

*fix column header issues in preview
*handle arbitrary whitespace

Hi @lumpyzhu ,

Glad to know this scientific computing library. However, you may need to provide a fully documented version before your release.

Describe the use case that is addressed by this feature.
Unlike roi_masks.calculate_traces(), demixer.demix_time_dep_masks() loads full image stack into memory to reshape it. Stacks can easily be > 50 GB, causing an out of memory error on some machines. This is not necessary, as the frames are then used one by one.

Describe the solution you'd like
Load by blocks of frames instead

The documentation in your vignette and the documentation for convert2df refer to this file to discern which field tags are used:

http://www.bibliometrix.org/documents/Field_Tags_bibliometrix.pdf

This document does not contain the fields:

[1] "DT2" "PP" "DB" "AU_UN" "AU1_UN"
[6] "AU_UN_NR" "SR_FULL" "SR"

What are these tags?

It would be worth putting in things like RLang resources, Python and NumPy, and Jupyter Notebooks and the like! Programming is very important, and there are lots of free statistical programming languages and libraries out there.

The website shows a table of the design decisions made for each case study, as of #2015. For now, it is just hardcoded into code/website/index.html. We should instead build this table automatically so it is more maintainable.

(@smiths, I'm assigning this to you just so that someone has ownership of it. You can reassign as needed).

Using, for example, napoleon, the Python API docs could be improved to better list parameters and their types.

Note there seems to be an issue with numpy return types: https://stackoverflow.com/q/56620817/4069571

The FCM documentation states that config files (such as keywords.cfg) are located from the following list of paths:

• [$HOME/.fcm in some cases]
• $FCM/etc/fcm/<configfile>
• $HOME/.metomi/fcm/<configfile>

However, the Debian package for FCM (cf. here) installs the confing files to /etc/fcm (a choice which is not unreasonable), whilst it in

Add a state-contextual help or something to get detailed help.
This should be a link to documentation relevant to what the user is currently doing.

The link should be accessible via a small ? icon somewhere central (not the help menu, but maybe there as well ;) and keyboard shortcut (ctrl-f1)

The documentation (stubs) might be autogenerated by inspecting module's frontend bits for easy deve

The setup.py test command is being deprecated and should be replaced by a more universial way to run the tests. Also the tests should be able to run before installation of the code. This means the imported xrayutilities version should not be the systems one but the one built by setup.py.

All this should be a

Expressions like 2 * 5% would translate to 2 * (5/100). Percentages can only be appended to factors and just divides them by 100.

Expliquer :

• les différents composants (front, service d'export, base de données MongoDB, l'API GraphQL...)
• les liens et la communication entre les différents composants
• les différents conteneurs Docker

You can also check the coverage on the website:

https://codecov.io/gh/magpylib/magpylib

Locally, you can have an HTML test coverage report in your folder, after running Pytest with the following command:

 py.test --junitxml=test-results/magpylib/results.xml --cov-report html --cov-report term:skip-covered --cov=magpylib

Add tests that reach the missing lines until the Code co