Institute of Analysis and Scientific Computing

21. February 2024

We present our new Senior Scientist

Congratulations to Dr. Karl HOLLAUS on his new position as a Senior Scientist!

Dr. Karl HOLLAUS received his doctorate from Graz University of Technology in 2001 and was subsequently employed there as a project assistant. From 2009 to 2010 he was a research assistant at the Rheinisch-Westfälische Technische Hochschule Aachen RWTH Aachen, Germany, working with Prof. SCHÖBERL. Since 2010 he is a postdoc at the TU Wien in the research group Computational Mathematics in Engineering of Prof. SCHÖBERL.

His research interest is computational electromagnetics, in particular the finite element method for modeling electromagnetic field problems. So far, he has been able to acquire three FWF Principal Investigator Projects and several research projects and thus set up a small research group of his own. Such additional funds allowed us to create and finance this new position. We are pleased that he will support us as a Senior Scientist in research and teaching and wish him all the best for his new tasks!

Welcome to the Institute of Analysis and Scientific Computing (ASC) at the Faculty of Mathematics and Geoinformation of TU Wien!

Our institute currently comprises 19 research groups with more than 60 scientific staff members. In addition, more than 50 student assistants are employed to run the tutorial groups of our courses.

We actively conduct mathematical research in pure and applied mathematics with currently around 25 ongoing research projects. Most of our research topics are from the areas of Computational Science and Engineering as well as Quantum Physics and Quantum Technologies at TU Wien, our focus of attention being the further development of applied mathematics.

With more than 150 courses per academic year, we contribute a large part to the excellent mathematics education at TU Wien. We are pleased that our students can benefit from our outstanding teaching and pursue successful careers in industry or academia.

Finally, members of the institute actively participate in the popular science initiative TUForMath - Forum Mathematik an der TU Wien, opens an external URL in a new window. In addition to popular science evening lectures on current, interesting and entertaining topics related to mathematics, TUForMath offers numerous workshops for school classes, where pupils are shown in a playful way the influence of mathematics on our daily lives, on science and technology, art and culture as well as society and economy. All TUForMath offers are free of charge!

If you have any further questions, please do not hesitate to contact us!

With best regards,
Prof. Dirk PRAETORIUS

Univ.Prof. Dipl.-Math. Dr.techn.Dirk Praetorius

Head, Institute of Analysis and Scientific Computing

Phone: +43 1 58801 10150 Call Dirk Praetorius

Send email to Dirk Praetorius

Show room DA04L16 on the map , opens an external URL in a new window

https://www.asc.tuwien.ac.at/praetorius/ , opens an external URL in a new window

Teaching

Lectures for

Basics Bachelor Mathematics
Master Technical Mathematics
Service Teaching (Physics, Electrical Engineering, CSE, Geodesics)
Alignment course AKMATH

Research

A three dimensional velocity field of a flow around a cylinder

Pure and applied mathematics in conjunction with mechanical engineering and natural sciences.

Primary TU research interests:

Computational Science and Engineering
Quantum Physics and Quantum Technologies

Staff

ASC group foto on the rooftop of the Freihaus

Research units

Analysis (head: Prof. Ansgar JÜNGEL)
Numerical Analysis (head: Prof. Markus MELENK)
Scientific Computing and Modelling (head: Prof. Joachim SCHÖBERL)

ASC Links

TUW Links

Links

Contact

Institute of Analysis and Scientific Computing
Wiedner Hauptstraße 8–10
1040 Wien
Phone: +43 1 58801 101 01
E-Mail: contact@asc.tuwien.ac.at

How to reach us

U1/U4 Karlsplatz – exit Wiedner Hauptstraße
1/62/Badner Bahn Resselgasse

Our offices and seminar rooms are located in the Freihaus building, green tower on the 3rd, 4th and 6th floor.

Project Coordination

Dipl.-Ing.inMarie-Sophie Auzinger

Support for project administration and events (4th floor)

Phone: +43 1 58801 10107 Call Marie-Sophie Auzinger

Send email to Marie-Sophie Auzinger

IT Administration

Andreas CzinkBSc

IT matters (office on the 4th floor)

Phone: +43 1 58801 10161 Call Andreas Czink

Send email to Andreas Czink

Show room DA04L12 on the map , opens an external URL in a new window

Administration Office

Brigitte Ecker

Financial matters (office on the 4th floor)

Phone: +43 1 58801 10117 Call Brigitte Ecker

Send email to Brigitte Ecker

Show room DA04J22 on the map , opens an external URL in a new window

Administration Office

Dr.in phil.Rebecca Fischer

Business trips, homepage (office on the 6th floor)

Phone: +43 1 58801 10171 Call Rebecca Fischer

Send email to Rebecca Fischer

Show room DA06K24 on the map , opens an external URL in a new window

Administration Office

Denise HohenbühelB.A.

Personnel matters (office on the 3rd floor)

Phone: +43 1 58801 10106 Call Denise Hohenbühel

Send email to Denise Hohenbühel

Student Staff

Franziska Pauline RiedelBSc

Student Staff

Send email to Franziska Pauline Riedel

Contact

Institute of Analysis and Scientific Computing
Wiedner Hauptstraße 8–10
1040 Wien
Phone: +43 1 58801 101 01
E-Mail: contact@asc.tuwien.ac.at

How to reach us

U1/U4 Karlsplatz – exit Wiedner Hauptstraße
1/62/Badner Bahn Resselgasse

Our offices and seminar rooms are located in the Freihaus building, green tower on the 3rd, 4th and 6th floor.

Project Coordination

Dipl.-Ing.inMarie-Sophie Auzinger

Support for project administration and events (4th floor)

Phone: +43 1 58801 10107 Call Marie-Sophie Auzinger

Send email to Marie-Sophie Auzinger

IT Administration

Andreas CzinkBSc

IT matters (office on the 4th floor)

Phone: +43 1 58801 10161 Call Andreas Czink

Send email to Andreas Czink

Show room DA04L12 on the map , opens an external URL in a new window

Administration Office

Brigitte Ecker

Financial matters (office on the 4th floor)

Phone: +43 1 58801 10117 Call Brigitte Ecker

Send email to Brigitte Ecker

Show room DA04J22 on the map , opens an external URL in a new window

Administration Office

Dr.in phil.Rebecca Fischer

Business trips, homepage (office on the 6th floor)

Phone: +43 1 58801 10171 Call Rebecca Fischer

Send email to Rebecca Fischer

Show room DA06K24 on the map , opens an external URL in a new window

Administration Office

Denise HohenbühelB.A.

Personnel matters (office on the 3rd floor)

Phone: +43 1 58801 10106 Call Denise Hohenbühel

Send email to Denise Hohenbühel

Student Staff

Franziska Pauline RiedelBSc

Student Staff

Send email to Franziska Pauline Riedel

Name	Purpose	Lifetime	Type	Provider
CookieConsent	Saves your settings for the use of cookies on this website.	1 year	HTML	Homepage TU Wien
SimpleSAML	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	Login TU Wien
SimpleSAMLAuthToken	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	Login TU Wien
fe_typo_user	Is needed so that in case of a Typo3 frontend login the session ID is recognized to grant access to protected areas.	session	HTTP	Homepage TU Wien
staticfilecache	Is needed to optimize the delivery time of the website.	session	HTTP	Homepage TU Wien
JESSIONSID	Is needed so that in case of a LectureTube the session ID is recognized to grant access to protected areas.	session	HTTP	LectureTube TU Wien
_shibsession_lecturetube	This is needed to distinguish between the sessions of the logged-in users.	session	HTTP	LectureTube TU Wien

Name	Purpose	Lifetime	Type	Provider
_pk_id	Used to store a few details about the user such as the unique visitor ID.	13 months	HTML	Matomo TU Wien
_pk_ref	Is used to store the information of the users home website.	6 months	HTML	Matomo TU Wien
_pk_ses	Is needed to store temporary data of the visit.	30 minutes	HTML	Matomo TU Wien
nmstat	Is used to record the behaviour on the website. It is used to collect statistics about website usage, such as when the visitor last visited the website. The cookie does not contain any personal data and is only used for website analysis.	1000 days	HTML	Siteimprove
siteimproveses	Is used to track the sequence of pages that a visitor views during his/her visit to the website. The cookie does not contain any personal data and is used solely for website analysis.	session	HTTP	Siteimprove
AWSELB	Always occurs in pairs with siteimproveses (for load balancing on the provider server)	session	HTTP	Siteimprove

Name	Purpose	Lifetime	Type	Provider
_ga	Is needed to distinguish the sessions of the users from each other.	persistent	HTTP	Google Analytics
_gali	Is needed to determine which links are clicked on a page.	expires immediately	HTTP	Google Analytics
_gat	This is a function-related cookie, whose tasks may differ.	2 years	HTTP	Google Analytics
_gid	Is needed to distinguish users and create statistics.	24 hours	HTTP	Google Analytics
_gads	Required to enable websites to display advertising from Google, including personalized advertising.	13 months	HTTP	Google Analytics
_gac_	Required by advertisers to measure user activity and the performance of their advertising campaigns.	90 days	HTTP	Google Analytics
_gcl_	Required by advertisers to determine how often users who click on their ads end up taking an action on their website.	90 days	HTTP	Google Analytics
_gcl_au	Contains a randomly generated user ID.	90 days	HTTP	Google
_gcl_aw	Is set when users click on a Google ad on the website and contains information about which ad was clicked.	90 days	HTTP	Google
__utma	Is used to record visits and visitors.	2 years	HTTP	Google Analytics
__utmb	Is used to detect new visits.	30 minutes	HTTP	Google Analytics
__utmc	Is used in connection with __utmb to determine whether it is a new (recent) visit.	session	HTTP	Google Analytics
__utmd	Is used to store and track visitor journeys through the site and classifies them into groups (marketing/tracking).	1 second	HTTP	Google Analytics
__utmt	Is needed to limit the query rate on Google Analytics.	10 minutes	HTTP	Google Analytics
__utmz	Is needed to determine from which source/campaign visitors come.	6 months	HTTP	Google Analytics
__utmvc	Is needed to collect information about user behavior on multiple websites. This information is used to optimize the relevance of advertising on the website.	24 hours	HTTP	Google AdSense
utm_source	Is needed to tag URLs with parameters to identify the campaigns that forward traffic.	expires immediately	HTTP	Google Analytics
__utm.gif	Is needed to save browser details.	session	HTTP	Google Analytics
gtag	Is needed to perform remarketing.	30 days	HTTP	Google AdSense
id	Is needed to perform remarketing.	2 years	HTTP	Google AdWords
1P_JAR	Is needed to optimize advertising, provide ads that are relevant to users, improve campaign performance reports, or prevent users from seeing the same ads more than once.	2 years	HTTP	Google
AID	Is needed to activate targeted advertising.	2 years	HTTP	Google Analytics
ANID	Is needed to display Google ads on non-Google websites.	2 years	HTTP	Google AdSense
APISID	Unknown functionality	2 years	HTTP	Google Ads Optimization
AR	Is needed to profile visitors' interests and display relevant ads on other websites. This cookie works by uniquely identifying your browser and device.	2 years	HTTP	Google AdSense
CONSENT	Is needed to store the preferences of visitors and personalize advertising.	persistent	HTTP	Google
DSID	Is needed by DoubleClick for advertising displayed in various places on the web and used to store the preferences of users.	2 years	HTTP	Doubleclick
DV	Is needed to store user preferences and other information. This includes, in particular, the preferred language, the number of search results to be displayed on the page, and the decision whether or not to activate the Google SafeSearch filter.	2 years	HTTP	Google
HSID	Contains the Google account ID and the last login time of the user.	2 years	HTTP	Google
IDE	Is needed by DoubleClick to record and report the actions of users on the website after viewing or clicking on one of the provider's ads, with the purpose of measuring the effectiveness of an advertisement and displaying targeted advertisements to users.	2 years	HTTP	Doubleclick
LOGIN_INFO	Is used to store the credentials of users of Google services.	2 years	HTTP	Google
NID	Is used to store information about user settings.	6 months	HTTP	Google
OTZ	Is needed to link activities of visitors with other devices that are previously logged in via the Google account. In this way, advertising is tailored to different devices.	1 month	HTTP	Google
RUL	Is needed by DoubleClick to determine whether advertising has been displayed correctly in order to make marketing activities more efficient.	1 year	HTTP	Doubleclick
SAPISID	Is needed by YouTube to store user settings and to calculate user bandwidth.	persistent	HTTP	Google
SEARCH_SAMESITE	Enables servers to mitigate the risk of CSRF and information leakage attacks by specifying that a particular cookie may only be sent on requests originating from the same registerable domain.	6 months	HTTP	Google
SID	Contains the Google account ID and the last login time of the user.	2 years	HTTP	Google
SIDCC	Is needed to store information about user settings and information for Google Maps.	3 months	HTTP	Google
SSID	Is needed to collect visitor information for videos hosted by YouTube on Google Maps integrated maps.	persistent	HTTP	Google
__SECURE-1PAPISID	Is needed for targeting purposes to create a profile of the interests of website visitors.	2 years	HTTP	Google
__SECURE-1PSID	Is needed for targeting purposes to create a profile of the interests of website visitors.	2 years	HTTP	Google
__SECURE-3PAPISID	Is needed for targeting purposes to create a profile of the interests of website visitors.	2 years	HTTP	Google
__SECURE-3PSID	Is needed for targeting purposes to create a profile of the interests of website visitors.	2 years	HTTP	Google
__SECURE-3PSIDCC	Is needed for targeting purposes to create a profile of the interests of website visitors.	2 years	HTTP	Google
__SECURE-APISID	Is needed to profile the interests of website visitors in order to display relevant and personalized advertising through retargeting.	8 months	HTTP	Google
__SECURE-HSID	Is needed to secure digitally signed and encrypted data from the unique Google ID and to store the last login time that Google uses to identify visitors, prevent fraudulent use of login data, and protect visitor data from unauthorized parties. This may also be used for targeting purposes to display relevant and personalized advertising content.	8 months	HTTP	Google
__SECURE-SSID	Is needed to store information about how visitors use the site and about the ads they may have seen before visiting the site. Also used to customize ads on Google domains.	8 months	HTTP	Google
test_cookie	Is set as a test to check whether the browser allows cookies to be set. Does not contain any identification features.	15 minutes	HTTP	Google
VISITOR_INFO1_LIVE	Is needed by YouTube to store user settings and to calculate user bandwidth.	6 months	HTTP	Youtube
facebook	Is used to Enable ad delivery or retargeting	90 days	HTTP	Meta (Facebook)
__fb_chat_plugin	Is needed to store and track interactions (marketing/tracking).	persistent	HTTP	Meta (Facebook)
_js_datr	Is needed to save user settings.	2 years	HTTP	Meta (Facebook)
_fbc	Is needed to save the last visit (marketing/tracking).	2 years	HTTP	Meta (Facebook)
fbm	Is needed to store account data (marketing/tracking).	1 year	HTTP	Meta (Facebook)
xs	Is needed to store a unique session ID (marketing/tracking).	1 year	HTTP	Meta (Facebook)
wd	Is needed to log the screen resolution.	1 week	HTTP	Meta (Facebook)
fr	Is needed to serve ads and measure and improve their relevance.	3 months	HTTP	Meta (Facebook)
act	Is needed to store logged in users (marketing/tracking).	90 days	HTTP	Meta (Facebook)
_fbp	Is needed to store and track visits to various websites (marketing/tracking).	3 months	HTTP	Meta (Facebook)
datr	Is needed to identify the browser for security and website integrity purposes, including account recovery and identification of potentially compromised accounts.	2 years	HTTP	Meta (Facebook)
dpr	Is used for analysis purposes. Technical parameters are logged (e.g. aspect ratio and dimensions of the screen) so that Facebook apps can be displayed correctly.	1 week	HTTP	Meta (Facebook)
sb	Is needed to store browser details and security information of the Facebook account.	2 years	HTTP	Meta (Facebook)
dbln	Is needed to store browser details and security information of the Facebook account.	2 years	HTTP	Meta (Facebook)
spin	Is needed for promotional purposes and social campaign reporting.	session	HTTP	Meta (Facebook)
presence	Contains the "chat" status of logged in users.	1 month	HTTP	Meta (Facebook)
cppo	Is needed for statistical purposes.	90 days	HTTP	Meta (Facebook)
locale	Is needed to save the language settings.	session	HTTP	Meta (Facebook)
pl	Required for Facebook Pixel.	2 years	HTTP	Meta (Facebook)
lu	Required for Facebook Pixel.	2 years	HTTP	Meta (Facebook)
c_user	Required for Facebook Pixel.	3 months	HTTP	Meta (Facebook)
bcookie	Is needed to store browser data (marketing/tracking).	2 years	HTTP	LinkedIn
li_oatml	Is needed to identify LinkedIn members outside of LinkedIn for advertising and analytics purposes.	1 month	HTTP	LinkedIn
BizographicsOptOut	Is needed to save privacy settings.	10 years	HTTP	LinkedIn
li_sugr	Is needed to store browser data (marketing/tracking).	3 months	HTTP	LinkedIn
UserMatchHistory	Is needed to provide advertising or retargeting (marketing/tracking).	30 days	HTTP	LinkedIn
linkedin_oauth_	Is needed to provide cross-page functionality.	session	HTTP	LinkedIn
lidc	Is needed to store performed actions on the website (marketing/tracking).	1 day	HTTP	LinkedIn
bscookie	Is needed to store performed actions on the website (marketing/tracking).	2 years	HTTP	LinkedIn
X-LI-IDC	Is needed to provide cross-page functionality (marketing/tracking).	session	HTTP	LinkedIn
AnalyticsSyncHistory	Stores the time when the user was synchronized with the "lms_analytics" cookie.	30 days	HTTP	LinkedIn
lms_ads	Is needed to identify LinkedIn members outside of LinkedIn.	30 days	HTTP	LinkedIn
lms_analytics	Is needed to identify LinkedIn members for analytics purposes.	30 days	HTTP	LinkedIn
li_fat_id	Required for indirect member identification used for conversion tracking, retargeting and analytics.	30 days	HTTP	LinkedIn
U	Is needed to identify the browser.	3 months	HTTP	LinkedIn
_guid	Is needed to identify a LinkedIn member for advertising via Google Ads.	90 days	HTTP	LinkedIn