#🔒 Jupyter notebook

71 messages · Page 1 of 1 (latest)

idle barn
#

So from the past few weeks i has working on my uni assignment and the professor said the work must be traceable so i use jupyter notebook. today when i look for the timestamp to check when my code is written i cant any there any one could help me to check how to trace it

toxic elkBOT
#

@idle barn

Python help channel opened

Remember to:

  • Ask your Python question, not if you can ask or if there's an expert who can help.
  • Show a code sample as text (rather than a screenshot) and the error message, if you've got one.
  • Explain what you expect to happen and what actually happens.

:warning: Do not pip install anything that isn't related to your question, especially if asked to over DMs.

idle barn
#

this is the topic I am working on

#

it said last checkpoint does it mean that the code is recorded like VS code?

#

something like this to proof my work

mortal canopy
#

What the prof probably means is: Your work should be a sequence of cells, so that you can follow the progression from top to bottom

#

ie: The first cell does step 1, then second cell does step 2.

mortal canopy
#

Notebooks are meant to organize your work in a sequence of blocks of code (the blocks are notebook "cells").

idle barn
#

this is what he said in the readme

#

but when i upload it on github i cant track my work like the photo shown

mortal canopy
#

Ah.

mortal canopy
#

Which is the result of what happens when you make individual commits.

#

Have you committed anything?

idle barn
#

i run it before

mortal canopy
#

Your question isn't really a "jupyter" question, it's a git question.

idle barn
#

this is my first year doing Like actual progamming cuz i was using VB.net before

mortal canopy
#

With git, you save your work in "commits". The commits are pushed. Each commit stores the updated verison of the file.

#

So, what you're seeing in that screenshot is: the commits that changed each line of that file.

#

(this is confusing, I know)

idle barn
#

like the things changed in the file?

#

it only shows something like this

#

when i go for commits

mortal canopy
#

That means you've made one commit, yes.

#

Unfortunately, you didn't do what the teacher said.

#

The teacher said: "You need to have at least one individual commit per graded item"

idle barn
#

it is the same on VSCode

mortal canopy
#

And, you committed 3 weeks ago

#

So, you haven't committed your current work.

#

When is it due?

idle barn
#

so i have to upload my work everytime i code?

#

20/11

mortal canopy
mortal canopy
#

You "committed" 3 weeks ago. You haven't committed your current work.

#

Here's what I'd do:

#
  1. Make a backup copy of your work: copy your file somewhere else
#
  1. "Revert" the file to the version you committed 3 weeks ago.
#
  1. Make one change at a time to the file, and commit it, according to the instructions
#
  1. Commit and "push" it, so you can see the change in github.
#

You have 2-3 days to do this, no problem.

#

It is an important skill/lesson to learn: this is something professionals do.

idle barn
#

for the commit part

#

I commit the file everytime i wrote a part of the code in jupyter?

mortal canopy
#

Carefully.

idle barn
#

so after i finish this part of the code i press commit to the github folder?

#

am i understanding it correctly

mortal canopy
#

Do a little, commit, do a little more, commit

idle barn
#

so when i finish a part i download it and commit it by uploadint the files

mortal canopy
#

You already have the file, you don't need to upload a file. You're just committing new versions of the file.

#

In vscode, look for this icon on the left:

idle barn
mortal canopy
#

Yes. Hover over the file, hit + to "stage" it, then enter a meaningful message: your teacher gave you instructions on what to put in the message.

idle barn
#

everytime i finish a part i press commit

mortal canopy
#

You hit +, add a message, then commit

idle barn
#

tthx man

#

u save my ass

mortal canopy
#

This is important stuff, I use git all day long.

idle barn
#

my old skl we use Visual basic and we hand it in by usb

#

never ues github

#

just theory

mortal canopy
idle barn
#

yea

toxic elkBOT
#
Python help channel closed for inactivity

This help channel has been closed. Feel free to create a new post in #1035199133436354600. To maximize your chances of getting a response, check out this guide on asking good questions.