WEBVTT

00:00:00.000 --> 00:00:05.290 align:middle line:90%


00:00:05.290 --> 00:00:08.170 align:middle line:84%
In computational engineering,
the main record of research

00:00:08.170 --> 00:00:09.850 align:middle line:90%
is data.

00:00:09.850 --> 00:00:14.170 align:middle line:84%
So gathering data and
lots of it is really easy.

00:00:14.170 --> 00:00:18.100 align:middle line:84%
But keeping it ordered,
properly labelled,

00:00:18.100 --> 00:00:22.470 align:middle line:84%
and coming with descriptive
texts is often quite hard.

00:00:22.470 --> 00:00:26.850 align:middle line:84%
So what I tend to do is I
like to write about what I do.

00:00:26.850 --> 00:00:29.030 align:middle line:84%
I like to write
about my results.

00:00:29.030 --> 00:00:30.790 align:middle line:90%
So, for example, I would--

00:00:30.790 --> 00:00:34.090 align:middle line:84%
after conducting a study, I
would write a short report

00:00:34.090 --> 00:00:36.640 align:middle line:84%
or make a presentation
to show the others

00:00:36.640 --> 00:00:39.302 align:middle line:90%
and try to organise everything.

00:00:39.302 --> 00:00:44.030 align:middle line:90%


00:00:44.030 --> 00:00:46.760 align:middle line:84%
My work tends to be
very multidisciplinary.

00:00:46.760 --> 00:00:49.820 align:middle line:84%
What I mean by this
is that oftentimes,

00:00:49.820 --> 00:00:53.210 align:middle line:84%
I would work for a length
of time on a problem--

00:00:53.210 --> 00:00:55.700 align:middle line:84%
let's call it problem
A. Then I would

00:00:55.700 --> 00:00:58.550 align:middle line:84%
shift to a next
stage in problem B.

00:00:58.550 --> 00:01:01.460 align:middle line:84%
But when I need to
come back to problem A,

00:01:01.460 --> 00:01:05.960 align:middle line:84%
I find it really important to
have a secure record of where

00:01:05.960 --> 00:01:09.200 align:middle line:84%
I've been, what I've done so
far, what the data is so that I

00:01:09.200 --> 00:01:11.810 align:middle line:90%
can resume work smoothly.

00:01:11.810 --> 00:01:15.320 align:middle line:84%
Also, when I want to
publish something fast

00:01:15.320 --> 00:01:17.570 align:middle line:84%
which is really
important at sometimes,

00:01:17.570 --> 00:01:21.620 align:middle line:84%
and I would like to have a
fairly detailed record of what

00:01:21.620 --> 00:01:23.270 align:middle line:84%
the results have
been, what I've been

00:01:23.270 --> 00:01:27.320 align:middle line:84%
doing so that I can get those
results out as fast as I can.

00:01:27.320 --> 00:01:33.410 align:middle line:90%


00:01:33.410 --> 00:01:35.720 align:middle line:84%
On more than one
occasion, I wish

00:01:35.720 --> 00:01:40.430 align:middle line:84%
I have kept a better
record of my work.

00:01:40.430 --> 00:01:44.840 align:middle line:84%
For example, when I didn't have
a chance to prepare beforehand

00:01:44.840 --> 00:01:47.360 align:middle line:84%
for collecting the
data, the results

00:01:47.360 --> 00:01:51.740 align:middle line:84%
might end up in confusing
figures or plots

00:01:51.740 --> 00:01:55.410 align:middle line:90%
or generically named files.

00:01:55.410 --> 00:02:01.292 align:middle line:84%
Also, if I don't dedicate
time to organise the file

00:02:01.292 --> 00:02:03.500 align:middle line:84%
system in my computer, for
example, before collecting

00:02:03.500 --> 00:02:07.880 align:middle line:84%
data, that can also become
very confusing at times

00:02:07.880 --> 00:02:10.100 align:middle line:90%
and lead to inefficiencies.