Marie-Françoise Roy

Marie-Françoise Roy (born 28 April 1950 in Paris) is a French mathematician noted for her work in real algebraic geometry. She has been Professor of Mathematics at the University of Rennes 1 since 1985 and in 2009 was made a Chevalier of the French Legion of Honour.[1]

Marie-Françoise Roy
Marie-Francoise Roy 2009 in Oberwolfach
Born1950 (age 6970)
NationalityFrench
Alma materParis 13 University
Scientific career
FieldsMathematics
InstitutionsUniversity of Rennes 1
Doctoral advisorJean Benabou

Research

Roy works in real algebraic geometry in particular real spectra and, most recently, in complexity of algorithms in real algebraic geometry and also the applications.[2]

Education and career

Marie-Françoise Roy got her education at École Normale Supérieure de jeunes filles and was an assistant professor at Université Paris Nord during 1973.[3] She received her PhD at Université Paris Nord in 1980, supervised by Jean Benabou.[4]

From 1981 she spent two years at Abdou Moumouni University in Niger. In 1985 she became a professor at University of Rennes 1 in Rennes, France.

Service

Roy was president of Société Mathématique de France from 2004 to 2007.[5]

In 1986, Roy was one of the founders[6] of European Women in Mathematics (EWM), and was the convenor (president) of EWM 2009-2013.[7] In 1987 she co-founded the French organization for women in mathematics, Femmes et Mathématiques, and became the organization's first president.

Roy is scientific officer for Sub-Saharan Africa in Centre International de Mathématiques Pures et Appliquées, CIMPA.[8] Roy is president of Association d'Echanges Culturels Cesson Dankassari (Tarbiyya-Tatali) an organization working for joint activities in a commune Dan-Cassari in Niger and the French commune Cesson-Sévigné.

Selected publications

  • with Saugata Basu, Richard Pollack: Algorithms in real algebraic geometry. Springer 2003.pdf-file freely available for authors homepage
  • with Jacek Bochnak, Michel Coste: Real algebraic geometry. 2.Edition, Springer, Ergebnisse der Mathematik Bd. 36, 1998 (first in French 1. Edition 1987).
  • Three Problems in real algebraic geometry and their descendants. In: Engquist, Schmid: Mathematics unlimited- 2001 and beyond. Springer Verlag 2000, S. 991 (Hilberts 17th Problem, Algorithms, Topology of real algebraic varieties).
  • Géométrie algébrique réelle. In: Jean-Paul Pier (Hrsg.): Development of Mathematics 1950-2000. Birkhäuser 2000.
  • Introduction a la geometrie algebrique reelle, Cahiers Sem. Hist. Math., 1991, Online
gollark: Well, yes, but they're byte sequences.
gollark: I mean, it's better than C and stuff, and I wouldn't mind writing simple apps in it.
gollark: Speaking specifically about the error handling, it may be "simple", but it's only "simple" in the sense of "the compiler writers do less work". It's very easy to mess it up by forgetting the useless boilerplate line somewhere, or something like that.
gollark: Speaking more generally than the type system, Go is just really... anti-abstraction... with, well, the gimped type system, lack of much metaprogramming support, and weird special cases, and poor error handling.
gollark: - They may be working on them, but they initially claimed that they weren't necessary and they don't exist now. Also, I don't trust them to not do them wrong.- Ooookay then- Well, generics, for one: they *kind of exist* in that you can have generic maps, channels, slices, and arrays, but not anything else. Also this (https://fasterthanli.me/blog/2020/i-want-off-mr-golangs-wild-ride/), which is mostly about the file handling not being good since it tries to map on concepts which don't fit. Also channels having weird special syntax. Also `for` and `range` and `new` and `make` basically just being magic stuff which do whatever the compiler writers wanted with no consistency- see above- Because there's no generic number/comparable thing type. You would need to use `interface{}` or write a new function (with identical code) for every type you wanted to compare- You can change a signature somewhere and won't be alerted, but something else will break because the interface is no longer implemented- They are byte sequences. https://blog.golang.org/strings.- It's not. You need to put `if err != nil { return err }` everywhere.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.