According to the documentation of joblib.dump the function should return a list of filenames. However, as pointed out by Jan Katins if a file object is provided then no output is returned.

Is it a bug or a feature? Should the docs be updated or maybe

https://gi

Hi @jmcarpenter2,

Dear Swifter Folks,

Recently, i found the speed when using swifter is 5-10x slower than using vanilla pandas apply for case that the process is not vectorized (my case is doing text preprocessing).

The experiment is like this:

import pandas as pd
import swifter

def clean_text(text):
    text = text.strip()
    text = text.replace(' ', '_')
    retu

I am sorry but I don't know how to put it into an Issue format, so I have to explain it plainly.

Dear contributors,

It seems that every source file in Vc library has the following copyright notice:

/*  This file is part of the Vc library. {{{
Copyright © 2009-2015 XXX <xxx@example.com>
Redistribution and use in source and binary forms, with or without
modification, are permitte

The standard accelerate test suite, used by all the backends, can be quite slow. Several of the tests are significantly slower than the others, for example segmented folds and scans, which I believe is because the reference implementations are very inefficient. Writing some more efficient reference implementations (e.g. using Data.Vector.Unboxed) should help speed things up.

Looks like there's no example using vector types defined in cltypes while the doc itself for these types are not so understandable. There are many examples having kernels taking vector type arguments, but the python code is using the numpy type, instead of the defined vector type. E.g. https://github.com/inducer/pyopencl/blob/master/examples/demo_elementwise_complex.py

The docs generated for #431 at https://mratsim.github.io/Arraymancer/pca.html have broken formatting:

• Upstream bug on the type:
  
• Random bolding:
  and
  ![image](https:/

Add 'Best Practices For Package Developers using Futures' vignette with instructions on, for instance,

1. How to test code, e.g. run tests with plan(sequential) and plan(multisession) and don't assume that plan(multicore) is available.

2. Make sure to shut down PSOCK clusters at the end of examples and package tests, i.e. call plan(sequential) at the end (e.g. #327)

3. Avoid setti

Almost all of Kokkos should be noexcept, but let's break it up into pieces that can be tackled in reasonable-sized issues. This one is the most urgent.

When computing the isosurface, when 4 simplex edges crosses the isosurface, we add 2 triangles to the isosurface triangulation.

Right now we add these arbitrarily (in these 3 lines) but we should add them so that the curvature is minimized.

The current state o

Present license file does not look right. Need to change it to the correct one

The nonlinear solver from the Sundials library KINSol has the following default behavior:

KINSol limits the maximum Newton update if

|| scale * update ||_2 > max(1000 * || scale * u0 ||_2, 1).

This forces KINSol to take more steps than necessary in the linear case.

Providing the option KINSetMaxNewtonStep(kin_mem, max_step) changes the default behavior to

|| scale * upda

The problem is as follows:

Given an optimization model part which contains elements. Gid is specified as output format. If the elements of the optimization model part are not initialized (which may happen e.g. when no internal analyzer is defined), then the function GiDOutputProcess::ExecuteBeforeSolutionLoop will produce a seg-fault when it calls

`__initialize_results --> gid_io.h line 6

I am entering the subject as a non mathematician and non data scientist. I'm a potential user of your code who is looking to solve actual down to earth practical problems. While your code apparently beautifully includes a multitude of problems and algorithms, they are really wasted on me as I simply don't get the math, the lingo or the examples.

I therefore suggest you provide a few practical e

I see that here on SourceForge, there are all Documentations in PDF format archived in single downloadable files. However the source is not provided. Did you use LaTeX or any other MarkUp languages to generate these PDFs? I would appreciate if you could do either of these

• add a Documentation folder on [this repository](

• - slength
• - maxSize
• - size
• - snull
• - (!?)
• - (!)
• - index
• - index'
• - head'
• - shead'
• - last'
• - indexM
• - headM
• - sheadM
• - lastM
• - unconsM
• - unsnocM
• - slice
• - slice'
• - sliceM
• - sslice
• - sliceAt
• - `slic

For users who haven't done ParallelAccelerator.embed, there should be an easy way to compile the package from the REPL before the first time it is used in that Julia session. We should implement and document this.

We worked very hard to get everything working in Travis. this demonstrates how to build and run everything, but it would be ideal if we translated this information into documentation for how to build the dependencies.

The link within the feature bullet point:

• Cluster can be monitored and managed with web browser.

Is currently broken.

Thanks for your work :)