Major improvements for interpolation matrix.
Full Changelog: https://github.com/scientificcomputing/scifem/compare/v0.16.1...v0.16.0
" authors: - affiliation: Simula Research Laboratoy family-names: Henrik Finsberg - affiliation: Simula Research Laboratory family-names: "Jørgen Schartum Dokken" cff-version: 1.2.0 date-released: "2025-12-17" doi: 10.5281/zenodo.13784777 license: MIT repository-code: https://github.com/scientificcomputing/scifem/tree/v0.16.1 title: "scientificcomputing/scifem: v0.16.1" type: software version: v0.24.0 scientificcomputing-scifem-652ead4/CMakeLists.txt 0000664 0000000 0000000 00000005040 15254505324 0022204 0 ustar 00root root 0000000 0000000 cmake_minimum_required(VERSION 3.21) set(PROJECT_NAME scifem) # nanobind uses aligned deallocators only present on macOS > 10.14 if(APPLE) set(CMAKE_OSX_DEPLOYMENT_TARGET "10.14") endif() set(CMAKE_CXX_STANDARD 20) set(CMAKE_CXX_STANDARD_REQUIRED ON) set(CMAKE_CXX_EXTENSIONS OFF) project(${PROJECT_NAME} VERSION "0.1.0.0" LANGUAGES C CXX) if (WIN32) # Windows requires all symbols to be manually exported. # This flag exports all symbols automatically, as in Unix. set(CMAKE_WINDOWS_EXPORT_ALL_SYMBOLS TRUE) endif(WIN32) execute_process( COMMAND ${Python3_EXECUTABLE} -c "import os, sys, basix; sys.stdout.write(os.path.dirname(basix.__file__))" OUTPUT_VARIABLE BASIX_PY_DIR RESULT_VARIABLE BASIX_PY_COMMAND_RESULT ERROR_VARIABLE BASIX_ERROR_OUT OUTPUT_STRIP_TRAILING_WHITESPACE ) find_package(Basix REQUIRED CONFIG HINTS ${BASIX_PY_DIR}) if(Basix_FOUND) message(STATUS "Found Basix at ${Basix_DIR}") endif() find_package(DOLFINX REQUIRED CONFIG) if(DOLFINX_FOUND) message(STATUS "Found DOLFINx at ${DOLFINX_DIR} (Version: ${DOLFINX_VERSION})") endif() find_package(Python COMPONENTS Interpreter Development.Module ${SKBUILD_SABI_COMPONENT} REQUIRED) # Detect the installed nanobind package and import it into CMake execute_process( COMMAND "${Python_EXECUTABLE}" -c "import nanobind; print(nanobind.cmake_dir())" OUTPUT_STRIP_TRAILING_WHITESPACE OUTPUT_VARIABLE NB_DIR) list(APPEND CMAKE_PREFIX_PATH "${NB_DIR}") find_package(nanobind CONFIG REQUIRED) if(NOT "${SKBUILD_SABI_VERSION}" STREQUAL "") set(NANOBIND_SABI "STABLE_ABI") endif() # We are now ready to compile the actual extension module nanobind_add_module( _scifem ${NANOBIND_SABI} src/scifem.cpp ) if(NANOBIND_SABI) # mpi4py and petsc4py use generated Cython headers so tell # them that the limited API is in use. target_compile_definitions(_scifem PRIVATE MPI4PY_LIMITED_API=1) # Needing to set CYTHON_COMPILING_IN_LIMITED_API is a bug in # Cython-generated API headers, should become unnecessary with # mpi4py/petsc4py releases published using Cython >= 3.1.4 # https://github.com/cython/cython/issues/7108 target_compile_definitions(_scifem PRIVATE CYTHON_COMPILING_IN_LIMITED_API=1) endif() if(DOLFINX_VERSION VERSION_GREATER_EQUAL "0.12.0.0") target_link_libraries(_scifem PRIVATE dolfinx::dolfinx) else() target_link_libraries(_scifem PRIVATE dolfinx) endif() set_target_properties(_scifem PROPERTIES INSTALL_RPATH_USE_LINK_PATH TRUE) # Install directive for scikit-build-core install(TARGETS _scifem LIBRARY DESTINATION ${PROJECT_NAME}) scientificcomputing-scifem-652ead4/CODE_OF_CONDUCT.md 0000664 0000000 0000000 00000011422 15254505324 0022244 0 ustar 00root root 0000000 0000000 # Code of Conduct ## Our Pledge In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. ## Our Standards Examples of behavior that contributes to a positive environment for our community include: - Demonstrating empathy and kindness toward other people - Being respectful of differing opinions, viewpoints, and experiences - Giving and gracefully accepting constructive feedback - Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience - Focusing on what is best not just for us as individuals, but for the overall community Examples of unacceptable behavior include: - The use of sexualized language or imagery, and sexual attention or advances - Trolling, insulting or derogatory comments, and personal or political attacks - Public or private harassment - Publishing others’ private information, such as a physical or email address, without their explicit permission - Other conduct which could reasonably be considered inappropriate in a professional setting ## Our Responsibilities Project maintainers are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful. Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate. ## Scope This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. ## Enforcement Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders. All complaints will be reviewed and investigated promptly and fairly. All community leaders are obligated to respect the privacy and security of the reporter of any incident. ## Enforcement Guidelines Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct: ### 1. Correction **Community Impact:** Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community. **Consequence:** A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested. ### 2. Warning **Community Impact:** A violation through a single incident or series of actions. **Consequence:** A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban. ### 3. Temporary Ban **Community Impact:** A serious violation of community standards, including sustained inappropriate behavior. **Consequence:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban. ### 4. Permanent Ban **Community Impact:** Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals. **Consequence:** A permanent ban from any sort of public interaction within the community. ## Attribution This Code of Conduct is adapted from the [Contributor Covenant](https://contributor-covenant.org/), version [1.4](https://www.contributor-covenant.org/version/1/4/code-of-conduct/code_of_conduct.md) and [2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/code_of_conduct.md, and was generated by [contributing-gen](https://github.com/bttger/contributing-gen). scientificcomputing-scifem-652ead4/CONTRIBUTING.md 0000664 0000000 0000000 00000017500 15254505324 0021701 0 ustar 00root root 0000000 0000000 # Contributing When contributing to this repository, please first [create an issue](https://github.com/scientificcomputing/scifem/issues/new/choose) containing information about the missing feature or the bug that you would like to fix. Here you can discuss the change you want to make with the maintainers of the repository. Please note we have a code of conduct, please follow it in all your interactions with the project. ## Adding a new feature We really appreciate contributions to the project. If you want to add a new feature, please create an issue first to discuss the feature you would like to add. This way we can make sure that the feature is in line with the goals of the project and that it is not already being worked on by someone else. Any new feature should be accompanied by tests and an example that should be part of the documentation. The tests should be added to the test suite in the `tests` folder and the example should be added to the `examples` folder, and added to the `_toc.yml` file so that it is included in the documentation. ## New contributor guide To get an overview of the project, read the [documentation](https://scientificcomputing.github.io/scifem/). Here are some resources to help you get started with open source contributions: - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github) - [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git) - [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) - [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests) ## Pull Request Process ### Pull Request - When you're finished with the changes, create a pull request, also known as a PR. It is also OK to create a [draft pull request](https://github.blog/2019-02-14-introducing-draft-pull-requests/) from the very beginning. Once you are done you can click on the ["Ready for review"] button. You can also [request a review](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/requesting-a-pull-request-review) from one of the maintainers. - Don't forget to [link PR to the issue that you opened ](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue). - Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge. Once you submit your PR, a team member will review your proposal. We may ask questions or request for additional information. - We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch. - As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations). - If you run into any merge issues, checkout this [git tutorial](https://lab.github.com/githubtraining/managing-merge-conflicts) to help you resolve merge conflicts and other issues. - Please make sure that all tests are passing, github pages renders nicely, and code coverage are are not lower than before your contribution. You see the different github action workflows by clicking the "Action" tab in the GitHub repository. ### Enforced style guide using pre-commit hooks We want to have a consistent style on all the contributions to the repository. The way we enforce this is through pre-commit hooks and contributors are encouraged to install the pre-commit hooks locally when developing. You can install the pre commit hooks by first install `pre-commit` ``` python3 -m pip install pre-commit ``` and then install the pre-commit hooks using the command ``` pre-commit install ``` at the root of the repository. This will install all the hooks listed in the file called `.pre-commit-config.yaml` in the root of the repository. Every time you make a commit to the repository a set of tests will run to make sure that the changes you made are following the style guide. Usually, the hooks will autoformat your code so that you only need to do a `git add` again and then redo the `git commit`. Note that when you make a push to the repo, the pre-commit hooks will be run on all the files in the repository. You can also run the pre-commit hooks on all the files using the command ``` pre-commit run --all ``` To learn more about pre-commit you can check out https://pre-commit.com ## Building from source `scifem` has a compiled component, so building it needs `scikit-build-core`, `nanobind` and the rest of the build backend. These are declared twice in `pyproject.toml`: in `[build-system].requires`, which `pip` installs automatically into an isolated build environment, and in the `build` [dependency group](https://peps.python.org/pep-0735/), which you install yourself when that isolation is turned off. Isolation is usually turned off when building against an existing DOLFINx, because a fresh build environment would pull in a second, incompatible `nanobind`. In that case install the build group first: ``` python3 -m pip install --group build python3 -m pip install --no-build-isolation --check-build-dependencies -e ".[all]" ``` Both commands are run from the root of the repository, since `--group` reads the `pyproject.toml` in the current directory. It needs `pip >= 25.1`. The two lists have to be kept in sync by hand; if you change one, change the other. ## Test suite For every new feature of bugfix you should also make sure to not lower the code coverage for the test suite. This means that if you for example add a new function then you should also make sure that the function is properly tested (at a minimum it should be covered by the test suite). To run the test suite, please install the package with the optional dependencies `test`, i.e ``` python3 -m pip install -e ".[all]" ``` in the root of the repository, or the `--no-build-isolation` variant above. To run the tests you can execute the command ``` python3 -m pytest ``` Also make to sure to check that the tests also passes with `mpiexec` by running ``` mpiexec -n 2 python3 -m pytest ``` Note that we have a [GitHub action](https://github.com/scientificcomputing/scifem/blob/main/.github/workflows/tests.yml) that runs the tests on every push and pull request to the main branch of the repository. You can read more about using pytest in the [official documentation of pytest](https://docs.pytest.org/). ## Documentation The documentation is hosted at GitHub pages and created with [`JupyterBook`](https://jupyterbook.org/en/stable/intro.html). Contributions to the documentation is very welcomed. To build the documentation locally you can install the `docs` optional dependencies, i.e ``` python3 -m pip install -e ".[docs]" ``` in the root of the repository. Now you can build the documentation by running the command ``` jupyter-book build . ``` from the root of the repository. The command should complete without errors or warnings. In particular, you might want to run the command ``` jupyter-book build -W --keep-going . ``` which will turn warnings into errors. For reference, please see the [github workflow](https://github.com/scientificcomputing/scifem/blob/main/.github/workflows/deploy_docs.yml) that is used for building the pages. ## Need help? If something is not working as expected, or you need help please file an [issue](https://github.com/scientificcomputing/scifem/issues/new/choose). scientificcomputing-scifem-652ead4/LICENSE 0000664 0000000 0000000 00000002123 15254505324 0020450 0 ustar 00root root 0000000 0000000 MIT License Copyright (c) 2024 Scientific Computing at Simula Research Laboratory Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. scientificcomputing-scifem-652ead4/README.md 0000664 0000000 0000000 00000012244 15254505324 0020727 0 ustar 00root root 0000000 0000000 # Scientific Computing Tools for Finite Element Methods This package contains a collection of tools for scientific computing with a focus on finite element methods. The tools are written in Python and are intended to be used in conjunction with the [dolfinx](https://github.com/FEniCS/dolfinx). Many users that are transitioning from legacy FEniCS to FEniCSx may find the transition difficult due to the lack of some functionalities in FEniCSx. This package aims to provide some of the functionalities that are missing in FEniCSx. See the [documentation](https://scientificcomputing.github.io/scifem/) for the API reference and runnable examples of the features below. ## Backwards compatibility We aim to support the last two stable releases of DOLFINx. Sometimes features are supported for longer if need be. Some features might depend on functionality added to DOLFINx, which means that they won't be backwards compatible. ## Features ### Meshes, tags and submeshes - Create `MeshTags` from a list of tags and corresponding locator functions. - Extract a submesh of entities of any co-dimension. - Locate the interface between two subdomains, and the exterior facets of a subdomain. ### Periodic meshes - Build a periodic mesh (MPI supported), by merging the vertices on opposite sides of the domain. The periodicity lives in the topology, so a continuous function space on the result is periodic with no constraint matrix, as opposed to [DOLFINx_MPC](https://github.com/jorgensd/dolfinx_mpc). - Take the vertex pairs from the `$Periodic` section of a gmsh model rather than from the coordinates. - Move mesh tags onto a periodic mesh, and move a solution back onto the mesh it was built from. Required for post-processing with Pyvista or Paraview. - Diagnose the two ways an input mesh can be unsuitable, a missing ghost layer and cells that collapse onto each other across a seam. ### Function spaces and degrees of freedom - Spaces of functions that are constant on each subdomain. - Maps between degrees of freedom and vertices, in both directions. ### Assembly, sources and boundary conditions - Assemble a scalar or a norm over all processes in a single call. - Point sources for usage in DOLFINx (>=v0.8.0). - Point sources in vector spaces are only supported on v0.9.0, post [DOLFINx PR 3429](https://github.com/FEniCS/dolfinx/pull/3429). For older versions, apply one point source in each sub space. - Interpolate an expression onto the degrees of freedom of a set of facets. - Helpers for the PETSc vector operations that surround a solve: zeroing, ghost updates, lifting and boundary conditions. ### Evaluation, interpolation and geometry - Evaluate a function at arbitrary points, in parallel. - Find the extrema of a UFL expression within each cell, or over a whole domain. - Project points onto the closest point of a mesh. - Build interpolation matrices from any `ufl.core.expr.Expr` into a compatible space. ### Output - Save quadrature functions as point clouds. - Save any function that can tabulate dof coordinates as point clouds. ### Biomedical - Read MRI data onto a mesh, as a function or as cell tags. Requires the `biomed` extra. ## Installation The package is partly written in C++ and relies on `dolfinx`. Users are encouraged to install `scifem` with `pip` in an environment where `dolfinx` is already installed or with `conda`. ### `pip` To install the package with `pip` run ```bash python3 -m pip install scifem --no-build-isolation ``` To install the development version you can run ```bash python3 -m pip install --no-build-isolation git+https://github.com/scientificcomputing/scifem.git ``` Note that you should pass the flag `--no-build-isolation` to `pip` to avoid issues with the build environment, such as incompatible versions of `nanobind`. ### `spack` The spack package manager is the recommended way to install scifem, and especially on HPC systems. For information about the package see: [spack-package: py-scifem](https://packages.spack.io/package.html?name=py-scifem) First, clone the spack repository and enable spack ```bash git clone --depth=2 https://github.com/spack/spack.git # For bash/zsh/sh . spack/share/spack/setup-env.sh # For tcsh/csh source spack/share/spack/setup-env.csh # For fish . spack/share/spack/setup-env.fish ``` Next create an environment: ```bash spack env create scifem_env spack env activate scifem_env ``` Find the compilers on the system ```bash spack compiler find ``` and install the relevant packages ```bash spack add py-scifem+petsc+hdf5+biomed+adios2 ^mpich ^petsc+mumps+hypre ^py-fenics-dolfinx+petsc4py spack concretize spack install ``` Finally, note that spack needs some packages already installed on your system. On a clean ubuntu container for example one needs to install the following packages before running spack ```bash apt update && apt install gcc unzip git python3-dev g++ gfortran xz-utils -y ``` ### `conda` To install the package with `conda` run ```bash conda install -c conda-forge scifem ``` ## Having issues or want to contribute? If you are having issues, feature request or would like to contribute, please let us know. You can do so by opening an issue on the [issue tracker](https://github.com/scientificcomputing/scifem/issues). scientificcomputing-scifem-652ead4/_config.yml 0000664 0000000 0000000 00000003434 15254505324 0021600 0 ustar 00root root 0000000 0000000 # Book settings # Learn more at https://jupyterbook.org/customize/config.html title: scifem author: Jørgen Dokken and Henrik Finsberg copyright: "2024" only_build_toc_files: true execute: execute_notebooks: cache timeout: 3000 # Information about where the book exists on the web repository: url: https://github.com/scientificcomputing/scifem # Online location of your book branch: main html: use_issues_button: true use_repository_button: true parse: myst_enable_extensions: - amsmath - dollarmath - linkify - html_admonition sphinx: extra_extensions: - 'sphinx.ext.autodoc' - 'sphinx.ext.napoleon' - 'sphinx.ext.viewcode' - 'sphinxcontrib.bibtex' - 'sphinx.ext.intersphinx' - "sphinx_codeautolink" config: html_last_updated_fmt: "%b %d, %Y" nb_execution_show_tb: True bibtex_bibfiles: ["docs/refs.bib"] suppress_warnings: ["mystnb.unknown_mime_type"] nb_custom_formats: # https://jupyterbook.org/en/stable/file-types/jupytext.html#file-types-custom .py: - jupytext.reads - fmt: py codeautolink_concat_default: True intersphinx_mapping: basix : ["https://docs.fenicsproject.org/basix/main/python/", null] ffcx : ["https://docs.fenicsproject.org/ffcx/main/", null] ufl : ["https://docs.fenicsproject.org/ufl/main/", null] dolfinx : ["https://docs.fenicsproject.org/dolfinx/main/python", null] petsc4py: ["https://petsc.org/release/petsc4py", null] mpi4py: ["https://mpi4py.readthedocs.io/en/stable", null] numpy: ["https://numpy.org/doc/stable/", null] pyvista: ["https://docs.pyvista.org/", null] packaging: ["https://packaging.pypa.io/en/stable/", null] exclude_patterns: [".pytest_cache/*" ,"tests", venv, .vcode, .ruff_cache, .github, .git] scientificcomputing-scifem-652ead4/_toc.yml 0000664 0000000 0000000 00000001555 15254505324 0021122 0 ustar 00root root 0000000 0000000 # Table of contents # Learn more at https://jupyterbook.org/customize/toc.html format: jb-book root: README parts: - caption: Periodic meshes chapters: - file: "examples/periodic_poisson.py" - file: "examples/periodic_heat_gmsh.py" - caption: Sources and evaluation chapters: - file: "examples/point_source.py" - file: "examples/evaluate_function.py" - caption: Output chapters: - file: "examples/xdmf_point_cloud.py" - caption: Meshes and tags chapters: - file: "examples/mark_entities.py" - file: "examples/transfer_tags_to_submesh" - caption: Function spaces and solvers chapters: - file: "examples/real_function_space.py" - file: "examples/blocked_solver.py" - caption: Reference chapters: - file: "docs/api.rst" - file: CONTRIBUTING - file: CODE_OF_CONDUCT scientificcomputing-scifem-652ead4/docs/ 0000775 0000000 0000000 00000000000 15254505324 0020375 5 ustar 00root root 0000000 0000000 scientificcomputing-scifem-652ead4/docs/_static/ 0000775 0000000 0000000 00000000000 15254505324 0022023 5 ustar 00root root 0000000 0000000 scientificcomputing-scifem-652ead4/docs/_static/cos_sin_pointcloud.png 0000664 0000000 0000000 00003405756 15254505324 0026452 0 ustar 00root root 0000000 0000000 PNG IHDR 2 Rw sBIT|d tEXtSoftware gnome-screenshot> /tEXtCreation Time s. 22. sep. 2024 kl. 18.40 +0200J IDATxwti{GJR-۵\^w+ET: " Hoj$@zN }Zɜ3'g6tщĜsc)x9"""""""""""""rQ"SDDDDDDDDDDDDD.8JdGLw """""""""""""'fwwwf3 Ӊfͦ8\!..@EDDDDDDDDDDDDbt=JAAq()""""""""""""R / 5ڮ|Nפ """""""""""""0 8i鉟VGP"SDDDDDDDDDDDDz{www|||G-P"SDDDDDDDDDDDD nnnyx&OO:%WP"SDDDDD俑wW+k~M;%oo b_z Fc)NJ^N 4+"""""RhN/j߶?fڊG..cF.iao礪1onR:* SZyub$#LeÝغgW 3p'/x qgYgSP{zFBӆ>PJ|,=l-W1 aхhb_|{*9+}. +G9}-?~3 Mt ;-M!iv ؽw-NA˘+|_DDDDD\l6cX^, f8&MTS{ F^z y.<8 e?V'%2EDDDDDjăpx_j+m/Mtz| I]9sX9Wr @.m.vdh2R`?# ~/ngap.\$ zcIQaRs jK!V^{1{eX M}1lLZ;8_hQ%\5Cܝ? GGaWG\y/E civ91h4Ff;vh\ M^q># ;` cȘ&N-.bu })2:S@lQ<'i 2EDDDDNe5M V'%7] য়~b0g }oqVq()"""""R+vv3 О_}t C!w#7#"sI&6-ӗ_gnb!bϻ׳ c.&#qOoj K3128[έ LM4)f XM[GM^q#/n) &sטKhj&F*E\؍#_6⌹/GͥSKOiʓ>&7c+.n,~`XL4 |?)hM˹HL|~^Ք_}Ci,xB|6M ҆O^tRg}~G W5ęY/=+vsCDδ`-X!/}O{ ڠ ݛ zlv}6le˖o߾4EpPZZoq2Y8#[Vۻu JOC܊L+(&Tx{Gvc DW dY- G)!mW9?$3(b [[dsg,et!^4#G lܓO5'd/dͪX{w!UkB(h&:²݀#c vY3#:ХA$ t= G@V '_E@Z%+͝+1MC@!6g N]ii137oa$mژ:=5*;D:(L!%C2a 7uoÓ6Gur4~ɽmSN{.+"""""`0T9gUۜ(Yq,Z}+rP5g3oHL ae1d:me31^Ǹk^fM!c)촏a|}k?E}{Uەq1:n :h-s~ưa: LӏA3_7o̥ ]+v07@kOwvmL! m!m;BL֮dSə4 ,Afy,eύjg9H[ N[ERz֬-m[a?>sP,pdpz !!VDoE,[#/_ё x[ `5)6ۑ_nRϷ+*""""""SLZ1v|L>i?ʏ/a5;^Ss*ڼ,ۦNVζk6m 8+S:~iCL|V|3Cd-ÀО?O{0F8z`%+E&mت%N pR GNѤv,`/(< GK Eө(FmǟxkW-yݼ; zⳣi{cܸd8/o)ٵ zNrfI38&'= 1j }o5Z w?,M)""""t sbZ93kO%2EDDDDDjʼnnn[⯧ͺ4__f=;-utvҌOUo8ļC?^ɰmp̟2*Ng.Hu D~Y-Q89 x/ P /1uӼd|5m%d<[a:.E7 Ű98 dcs%0 b $,#N2ȫ [_kt˯! ;72 ENp 9DI1ݻ ҏ?yѱ&| {ȅf^kU Z Vk6L:\ ǐ!CʝĜ%3CLZ+~ 4 #vჯq̜I OHVDPs ~ :47g *m.؆[|2s7p Ai2iǴe$]=G g"4V2+o4PGV䔓.u QHG1J~~ƈqp} XYMch&aW&VGB ;v|-m33A`rض~; :ʛq[}2y+# 9yictI^re"nDSX*?ͨX3ǖ 56 """""}DeUJKK]ToNh4ҿ<1gf7o CLstN ~ _M ā\?U>i+\W3vs]-gjrfCshxc߲l0