1,720,973 research outputs found

    Raw data related to publication "Influence of engineered roughness microstructures on adhesion and turbulent resuspension of microparticles" by Banari et al. (2023)

    No full text
    #Folder "Adhesion": Contains all raw data related to the adhesion force measurement. To plot the figure, run python3. plot.py #Folder "SEM": each subfolder S1, S2 and S3 contains further high-resolution pictures taken with the SEM #Folder "WindChannel": Contains all raw data related to the resuspensiob experiment performed in the winf channel. More Info in Windchannel/Readme.tx

    Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model

    No full text
    Source files and selected raw data related to the manuscript "Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model" by Gregory Lecrivain, Helmholtz-Zentrum Dresden-Rossendorf, Germany, 2024. 1) folder "manuscript", This folder contains all text documents related to manuscript. Text and final figures are found in the directory. 2) folder "scripts" This folder contains python and bash scripts used to post-process the raw data and prepare the figures. You will need to install some python3 libraries. Use the following command: pip install pyquaternion matplotlib scipy intersect. 3) folder "figures" This folder contain information on how to run the simulations related to the figure. More information can be found in the README text file located in each figure/figX subfolder, where X the figure number in the manuscript. 4) folder "src" This folder contains the all c++ files related to the source code. 4.1) Prior to compiling, you should have gcc(7.3.0), openmpi(2.1.2), make(4.3), cmake(3.20.2), python(3.8.0), blas(3.8.0), lapack(3.8.0), boost(1.78.0), and git(2.30.1) available on your machine. The version number in the parenthesis corresponds to the one I used on the local HPC available at my institution. In my case, I type "module load gcc/7.3.0 openmpi/2.1.2 make/4.3 cmake/3.20.2 python/3.8.0 blas/3.8.0 lapack/3.8.0 boost/1.78.0 git/2.30.1". 4.2) To compile the libraries, open a terminal, cd to the src directory and type "make libs". All outputs will placed in the folder HOME/local.ThelibrariestarballsneededtocompilethecodeareplacedintheLibsdirectory.4.3)Ihavemanuallyinstalledparaview5.9.1.pvpythonisusedtoexporttxtdata(hinge,dropandthreephasecontactline)tovtkformat.4.4)Openyour /.bashrcfileandaddthefollowinglines.exportIGLNUMTHREADS=1exportLDLIBRARYPATH=HOME/local. The libraries' tarballs needed to compile the code are placed in the Libs directory. 4.3) I have manually installed paraview 5.9.1. pvpython is used to export txt data (hinge, drop and three-phase contact line) to vtk format. 4.4) Open your ~/.bashrc file and add the following lines. export IGL_NUM_THREADS=1 export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/libconfig1.7.3/libexportLDLIBRARYPATH=HOME/local/libconfig-1.7.3/lib export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/gmp6.2.1/libexportLDLIBRARYPATH=HOME/local/gmp-6.2.1/lib export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/mpfr4.1.0/libexportPATH=HOME/local/mpfr-4.1.0/lib export PATH=PATH:HOME/microorigami/src #(or whereever, your chosen parent directory is) export PATH=PATH:HOME/microorigami/scripts #(or whereever, your chosen parent directory is) export PATH=PATH:$HOME/microorigami/paraview/bin #(or whatever path you used) 4.5) open a new terminal, cd to the src directory and type "make check_library_path". The terminal should return "library path to libconfig is correct" "library path to gmp is correct" "library path to mpfr is correct" If that is the case, i.e. the paths are correctly set. To compile, type "make main post". Alternatively, one can speed up the installation by typing "make -j 4 main post", where 4 is the number of cpus I use. 4.6) Help is available in each header file (.h) in the form of doxygen comments. Type "make doxy". The folder html will appear under src. 4.7) Type "make clean" to clean the src folder 5) folders "caX_sideY_ecZ.zip" The zip files contains the raw data related to Figure 10. Here, X = 70 is the contact angle, Y = 5 the number of side panels and Z = 0.8, 1.6 and 2.4 the elasto-capillary number. After data extraction, three folders will be created, namely wd/ca70/side5/ec0.8, wd/ca70/side5/ec1.6 and wd/ca70/side5/ec2.4, where wd is your working directory. To convert the data into human-readable format (txt, vtk, stl,...) type "source Utils.sh; ExportScript --verbose --submit" in the working directory wd on the hpc. The bash function ExportScript is located in "scripts/Utils.sh". All other raw data can be obtained by following the commands in the README text file located in each figX folder, with X=1,2,...,13. With Paraview, one is able to visualize the self-folding by loading the stl files

    Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model

    No full text
    Source files and selected raw data related to the manuscript "Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model" by Gregory Lecrivain, Helmholtz-Zentrum Dresden-Rossendorf, Germany, 2024. 1) folder "manuscript", This folder contains all text documents related to manuscript. Text and final figures are found in the directory. 2) folder "scripts" This folder contains python and bash scripts used to post process the raw data and prepare the figures.You will need to install some python3 libraries. Use the following command pip install pyquaternion matplotlib scipy intersect 3) folder "figures" This folder contain information on how to run the simulations related to the figure. More information in README file in each figure/figureX subfloder with X the figure number in the manuscript. 4) folder "src" This folder contains the all c++ files related to the source code. 4.1) Prior to compiling, you should have gcc(7.3.0), openmpi(2.1.2), make(4.3), cmake(3.20.2), python(3.8.0), blas(3.8.0), lapack(3.8.0), boost(1.78.0), and git(2.30.1) available on your machine. The version number in the parenthesis corresponds to the one I used on the local HPC available at my institution. In my case, I type "module load gcc/7.3.0 openmpi/2.1.2 make/4.3 cmake/3.20.2 python/3.8.0 blas/3.8.0 lapack/3.8.0 boost/1.78.0 git/2.30.1". 4.2) To compile the libraries, open a terminal, cd to the src directory and type "make libs". All outputs will placed in the folder HOME/local.ThelibrariestarballsneededtocompilethecodeareplacedintheLibsdirectory.4.3)Ihavemanuallyinstalledparaview5.9.1inHOME/local. The libraries' tarballs needed to compile the code are placed in the Libs directory. 4.3) I have manually installed paraview 5.9.1 in HOME/Paraview/ParaView-5.9.1-MPI-Linux-Python3.8-64bit/. pvpython is used to export txt data (hinge, drop and three-phase contact line) to vtk format. 4.4) Open your ~/.bashrc file and add the following lines. export IGL_NUM_THREADS=1 export LD_LIBRARY_PATH=LDLIBRARYPATH:LD_LIBRARY_PATH:HOME/local/libconfig-1.7.3/lib export LD_LIBRARY_PATH=LDLIBRARYPATH:LD_LIBRARY_PATH:HOME/local/gmp-6.2.1/lib export LD_LIBRARY_PATH=LDLIBRARYPATH:LD_LIBRARY_PATH:HOME/local/mpfr-4.1.0/lib export PATH=PATH:PATH:HOME/Documents/microorigami/src #(or whereever, your chosen parent directory is) export PATH=PATH:PATH:HOME/Documents/microorigami/scripts #(or whereever, your chosen parent directory is) export PATH=PATH:PATH:HOME/Documents/microorigami/paraview/bin #(or whatever path you used) 4.5) open a new terminal, cd to the src directory and type "make check_library_path". The terminal should return "library path to libconfig is correct" "library path to gmp is correct" "library path to mpfr is correct" If that is the case, i.e. the paths are correctly set. To compile, type "make main post". Alternatively, one can speed up the installation by typing "make -j 4 main post", where 4 is the number of cpus I use. 4.6) Help is available in each header file (.h) in the form of doxygen comments. Type "make doxy". The folder html will appear under src. 4.7) Type "make clean" to clean the src folder 5) folders "caX_sideY_ecZ.zip" The zip files contains, where where X = 70 is the contact angle, Y = 5 the number of side panels and Z = 0.8, 1.6 and 2.4 the elasto-capillary number, are selected raw data related to Figure 10. All other raw data can be reproduced by following the commands in the README text file located in each figX folder, with X=1,2,...,13. After extraction, three folders will be created, namely wd/ca70/side5/ec0.8, wd/ca70/side5/ec1.6 and wd/ca70/side5/ec2.4, where wd is your working directory. To convert the data into human-readable format (txt, vtk, stl,...) type "source Utils.sh; ExportScript --verbose --submit" in the working directory wd on the hpc. The bash function ExportScript is located in "scripts/Utils.sh"

    Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model

    No full text
    Source files and selected raw data related to the manuscript "Self-folding of two-dimensional thin templates into pyramidal micro-structures by a liquid drop - a numerical model" by Gregory Lecrivain, Helmholtz-Zentrum Dresden-Rossendorf, Germany, 2024. 1) folder "manuscript", This folder contains all text documents related to manuscript. Text and final figures are found in the directory. 2) folder "scripts" This folder contains python and bash scripts used to post-process the raw data and prepare the figures. You will need to install some python3 libraries. Use the following command: pip install pyquaternion matplotlib scipy intersect. 3) folder "figures" This folder contain information on how to run the simulations related to the figure. More information can be found in the README text file located in each figure/figX subfolder, where X the figure number in the manuscript. 4) folder "src" This folder contains the all c++ files related to the source code. 4.1) Prior to compiling, you should have gcc(7.3.0), openmpi(2.1.2), make(4.3), cmake(3.20.2), python(3.8.0), blas(3.8.0), lapack(3.8.0), boost(1.78.0), and git(2.30.1) available on your machine. The version number in the parenthesis corresponds to the one I used on the local HPC available at my institution. In my case, I type "module load gcc/7.3.0 openmpi/2.1.2 make/4.3 cmake/3.20.2 python/3.8.0 blas/3.8.0 lapack/3.8.0 boost/1.78.0 git/2.30.1". 4.2) To compile the libraries, open a terminal, cd to the src directory and type "make libs". All outputs will placed in the folder HOME/local.ThelibrariestarballsneededtocompilethecodeareplacedintheLibsdirectory.4.3)Ihavemanuallyinstalledparaview5.9.1.pvpythonisusedtoexporttxtdata(hinge,dropandthreephasecontactline)tovtkformat.4.4)Openyour /.bashrcfileandaddthefollowinglines.exportIGLNUMTHREADS=1exportLDLIBRARYPATH=HOME/local. The libraries' tarballs needed to compile the code are placed in the Libs directory. 4.3) I have manually installed paraview 5.9.1. pvpython is used to export txt data (hinge, drop and three-phase contact line) to vtk format. 4.4) Open your ~/.bashrc file and add the following lines. export IGL_NUM_THREADS=1 export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/libconfig1.7.3/libexportLDLIBRARYPATH=HOME/local/libconfig-1.7.3/lib export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/gmp6.2.1/libexportLDLIBRARYPATH=HOME/local/gmp-6.2.1/lib export LD_LIBRARY_PATH=LD_LIBRARY_PATH:HOME/local/mpfr4.1.0/libexportPATH=HOME/local/mpfr-4.1.0/lib export PATH=PATH:HOME/microorigami/src #(or whereever, your chosen parent directory is) export PATH=PATH:HOME/microorigami/scripts #(or whereever, your chosen parent directory is) export PATH=PATH:$HOME/microorigami/paraview/bin #(or whatever path you used) 4.5) open a new terminal, cd to the src directory and type "make check_library_path". The terminal should return "library path to libconfig is correct" "library path to gmp is correct" "library path to mpfr is correct" If that is the case, i.e. the paths are correctly set. To compile, type "make main post". Alternatively, one can speed up the installation by typing "make -j 4 main post", where 4 is the number of cpus I use. 4.6) Help is available in each header file (.h) in the form of doxygen comments. Type "make doxy". The folder html will appear under src. 4.7) Type "make clean" to clean the src folder 5) folders "caX_sideY_ecZ.zip" The zip files contains the raw data related to Figure 10. Here, X = 70 is the contact angle, Y = 5 the number of side panels and Z = 0.8, 1.6 and 2.4 the elasto-capillary number. After data extraction, three folders will be created, namely wd/ca70/side5/ec0.8, wd/ca70/side5/ec1.6 and wd/ca70/side5/ec2.4, where wd is your working directory. To convert the data into human-readable format (txt, vtk, stl,...) type "source Utils.sh; ExportScript --verbose --submit" in the working directory wd on the hpc. The bash function ExportScript is located in "scripts/Utils.sh". All other raw data can be obtained by following the commands in the README text file located in each figX folder, with X=1,2,...,13. With Paraview, one is able to visualize the self-folding by loading the stl files

    Raw data related to publication entitled "Turbulent resuspension of micron particles from a wall surface functionalized with cylindrical micropillars" by Banari, A. et al.

    No full text
    # 'Flowrate.JPG': Table associating a raw image (see 'org' folder below) with the flow rate (Q) in L/min # 'Rough': raw data obtained with the rough substrate # 'Smooth': raw data obtained with the smooth substrate # "Smooth" and "Rough" folders contain a list of subfolders Mi, with i=0,1,2,... the measurement index. Ex: M1: is a first series of measurements and M2: a second series of measurements. Each Mi folder contains the following data: ## 'org': List of pictures (Acquisition_AAA_-BBBBBB.jpg) taken with the high-resolution camera. With AAA=000,001,002,... is the flow rate association. To associate AAA with the flow rate, see 'Flowrate.JPG'. Ex: '000' -> Q = 0 L/min, '001' -> Q = 20 L/min. BBB=000001,000002 or 000003 are pictures of the same particle bed taken at increasing time interval. These 3 pictures are used to check particle bed equilibrium. ## 'pic_CCC.jpg' with CCC=001, 002, 003: simply a copy of the raw picture in 'org' with bed at equilibrium. The association between the index (CCC) and the flow rate (Q) is identical to that described in 'org' (AAA). ## 'Particles_CCC.csv' with CCC=001, 002, 003: List of particle positions (called tags in the manuscript) in each respective image

    Going Beyond Counting First Authors in Author Co-citation Analysis

    Get PDF
    The present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed

    Variations on the Author

    Get PDF
    “Variations on the Author” discusses two of Eduardo Coutinho’s recent films (Um Dia na Vida, from 2010, and Últimas Conversas, posthumously released in 2015) and their contribution to the general question of documentary authorship. The director’s filmography is characterized by a consistent yet self-effacing form of authorial self-inscription: Coutinho often features as an interviewer that rather than express opinions propels discourses; an interviewer that is good at listening. This mode of self-inscription characterizes him as an author who is not expressive but who is nonetheless markedly present on the screen. In Um Dia na Vida, however, Coutinho is completely absent form the image, while Últimas Conversas, on the contrary, includes a confessional prologue that moves the director from the margins to the center of his films. This article examines the ways in which these works stand out in the filmography of a director who offers new insights into the notion of cinematic authorship

    Appropriate Similarity Measures for Author Cocitation Analysis

    Get PDF
    We provide a number of new insights into the methodological discussion about author cocitation analysis. We first argue that the use of the Pearson correlation for measuring the similarity between authors’ cocitation profiles is not very satisfactory. We then discuss what kind of similarity measures may be used as an alternative to the Pearson correlation. We consider three similarity measures in particular. One is the well-known cosine. The other two similarity measures have not been used before in the bibliometric literature. Finally, we show by means of an example that our findings have a high practical relevance.information science;Pearson correlation;cosine;similarity measure;author cocitation analysis

    Dispelling the Myths Behind First-author Citation Counts

    Get PDF
    We conducted a full-scale evaluative citation analysis study of scholars in the XML research field to explore just how different from each other author rankings resulting from different citation counting methods actually are, and to demonstrate the capability of emerging data and tools on the Web in supporting more realistic citation counting methods. Our results contest some common arguments for the continued use of first-author citation counts in the evaluation of scholars, such as high correlations between author rankings by first-author citation counts and other citation counting methods, and high costs of using more realistic citation counting methods that are not well-supported by the ISI databases. It is argued that increasingly available digital full text research papers make it possible for citation analysis studies to go beyond what the ISI databases have directly supported and to employ more sophisticated methods
    corecore