fenics team mailing list archive

[Kristian Oelgaard <k.b.oelgaard@xxxxxxxxx>]

On 28 May 2010 19:54, Andy Ray Terrel <andy.terrel@xxxxxxxxx> wrote:
> On Fri, May 28, 2010 at 12:43 PM, Kristian Oelgaard
> <k.b.oelgaard@xxxxxxxxx> wrote:
>> On 28 May 2010 18:35, Anders Logg <logg@xxxxxxxxx> wrote:
>>> On Fri, May 28, 2010 at 11:18:53AM -0500, Andy Ray Terrel wrote:
>>>> On Fri, May 28, 2010 at 10:19 AM, Anders Logg <logg@xxxxxxxxx> wrote:
>>>> > On Fri, May 28, 2010 at 10:13:48AM -0500, Andy Ray Terrel wrote:
>>>> >> On Fri, May 28, 2010 at 9:12 AM, Anders Logg <logg@xxxxxxxxx> wrote:
>>>> >> > On Fri, May 28, 2010 at 08:43:07AM -0500, Andy Ray Terrel wrote:
>>>> >> >> Hello,
>>>> >> >>
>>>> >> >> I have agreed to give a FEniCS Tutorial at ESCO 2010 [0].  If anyone
>>>> >> >> is interested and in the area feel free to drop by.
>>>> >> >
>>>> >> > Cool. One thing to consider would be to have a common repository for
>>>> >> > tutorial material. I have some slides I can donate if you are
>>>> >> > interested.
>>>> >>
>>>> >> That would be excellent.  Matt and I have a system for our
>>>> >> presentations [0] we can model or we could just do like PETSc and put
>>>> >> tutorials up on the webpage.
>>>> >>
>>>> >> -- Andy
>>>> >>
>>>> >> [0] http://www.bitbucket.org/aterrel/presentations
>>>> >
>>>> > The slides I have are in the exact same format so it should be easy to
>>>> > merge. :-)
>>>> >
>>>> > Where are the PETSc tutorials? Are they written in HTML? I prefer
>>>> > writing in LaTeX.
>>>> >
>>>>
>>>> http://www.mcs.anl.gov/petsc/petsc-as/documentation/tutorials/index.html
>>>>
>>>> I think most are in latex but in some private repo.  Which is why Matt
>>>> and I have the separate reop.
>>>
>>> ok.
>>>
>>>> Should we set up another launchpad project or just incorporate it in
>>>> the fenics-doc?
>>>
>>> Don't know. It might clutter up that repo but it would be the easiest
>>> option. There's an administrative overhead to creating too many lp
>>> groups/projects.
>>
>> I guess it depends on how it is organised and maintained.
>> We could have 'presentations' on the same level as 'demos', 'tutorial'
>> and 'programmer's reference'.
>> But what I don't want is 200+ tutorials like this:
>>
>> demonstrating_poisson_at_foo_conference_by_bar_2010_05_15
>> demonstrating_poisson_at_foo_conference_by_bar_2010_07_23
>> demonstrating_poisson_at_foo_conference_by_bar_2010_07_25
>> demonstrating_poisson_at_foo_conference_by_bar_2010_07_26
>>
>> where 99% of the contents is the same and all the code examples are outdated.
>>
>> Preferably, we will have a handful of presentations which covers the
>> essentials from FEniCS: PDEs, la, mesh etc. with up to date code
>> examples. Then if someone needs a presentation, it's just a matter of
>> copy/paste with some minor tweaks to direct the presentation towards a
>> specific audience.
>>
>> Kristian
>
>
> Okay I would be more for a separate repo then.  Tutorials should be
> tailored to the audience which by its very nature leads to the
> numerous versions.  Matt and I mitigate the out of date bit by having
> (almost) every slide be an input.  Then when the slide gets used again
> it gets updated.
>
> I guess if there is a good reason to also have an "official"
> presentation, then that could be developed in parallel.

So would it be an idea to have the 'code slides' in the fenics-doc
repo, and then you can pull those bits that you need?

Kristian

> -- Andy
>
>>
>>> What does Kristian say? Garth?
>>>
>>> --
>>> Anders
>>>
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.10 (GNU/Linux)
>>>
>>> iEYEARECAAYFAkv/8NoACgkQTuwUCDsYZdGDSgCghwEQpd0M0Blr/7xksc0UEd2R
>>> 3asAn3o8Y24Z/6pZEx6ApWsH9eStgeMX
>>> =Fuov
>>> -----END PGP SIGNATURE-----
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~fenics
>>> Post to     : fenics@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~fenics
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>