<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02167nam a2200241Ia 4500</leader>
  <controlfield tag="003">MX-MdCICY</controlfield>
  <controlfield tag="005">20260521091535.0</controlfield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="c">CICY</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">B-16734</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">A fast multipole implementation of the simplified hybrid boundary element method: application to 2D potential problems</subfield>
  </datafield>
  <datafield tag="490" ind1="0" ind2=" ">
    <subfield code="v">European Journal of Computational Mechanics, 19 March, p.1-24, 2017</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">The ultimate subject of this work is the implementation and testing of a novel numerical tool that can simulate on a personal computer and only in a few minutes a problem with many millions of degrees of freedom. The authors have already successfully developed and tested a technique that turned out to be a modified, reverse fast-multipole implementation for the conventional BEM. The variationally based hybrid BEM leads to a computationally less intensive formulation than in the conventional BEM for large-scale 2D and 3D problems of potential and elasticity. This formulation is especially advantageous for problems of complicated geometry and topology or requiring complicated fundamental solutions. The proposed implementation of the fast multipole method (FMM)for the simplified, hybrid BEM deals with the transpose of the double-layer potential matrix as well as with the nodal matrix expression of the potential fundamental solution. The basic aspects of the FMM are firstly introduced for the conventional BEM as well as for its expedite version. This takes most part of the present paper, which ends up with some validating numerical results. The FMM outline for the simplified hybrid BEM is shown in a separate section, as its numerical implementation is still in progress.</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">BOUNDARY ELEMENTS</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">FAST MULTIPOLE METHOD</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">HYBRID BOUNDARY ELEMENTS</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">POTENTIAL PROBLEMS</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="4">
    <subfield code="a">VARIATIONAL METHODS</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Dumont, N.A.</subfield>
  </datafield>
  <datafield tag="700" ind1="1" ind2="2">
    <subfield code="a">Peixoto, H.D.F.C.</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2="0">
    <subfield code="u">https://drive.google.com/file/d/1ycnZu6VnesuySlHfUYMB2lB1YRRNtEmc/view?usp=drivesdk</subfield>
    <subfield code="z">Para ver el documento ingresa a Google con tu cuenta: @cicy.edu.mx</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">Loc</subfield>
    <subfield code="c">REF1</subfield>
  </datafield>
  <controlfield tag="008">250602s9999    xx |||||s2   |||| ||und|d</controlfield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">26840</subfield>
    <subfield code="d">26840</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">Loc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="8">F1</subfield>
    <subfield code="a">CICY</subfield>
    <subfield code="b">CICY</subfield>
    <subfield code="c">RE</subfield>
    <subfield code="d">2025-06-25</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">B-16734</subfield>
    <subfield code="r">2025-06-25 16:01:57</subfield>
    <subfield code="w">2025-06-25</subfield>
    <subfield code="y">REF1</subfield>
  </datafield>
</record>
