> --
> You received this message because you are subscribed to the Google Groups "sage-edu" group.
> To post to this group, send email to sage...@googlegroups.com.
> To unsubscribe from this group, send email to sage-edu+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/sage-edu?hl=en.
>
>
i use SAGE servers for graded work but only in class assignments done in groups for a group grade.
It is even worse if you are using a public SAGE server. Someone off campus could be sharing worksheets with your students...
----------
Sent from my Verizon Wireless mobile phone
Dmitrii,
Jonathan
--
Can you set up a Sage server locally,
(a) create one worksheet worksheet_x per student x (that you own),
the worksheet consisting of exam questions,
(b) share worksheet_x with x
(c) tell the student to save the work when they are done?
Even easier is to create one public worksheet that everyone must
manually copy into their account before editing. It's still pretty
easy to poke around and look at other people's worksheets if you know
how (via the filesystem, unless extra accounts are set up, and you
probably don't want to create 200 login accounts on the server) so I'd
say this works best with low-stakes problems where the goal is
experimentation. For code, I think projects usually make more sense
than exams.
- Robert
The nice thing about David's method is it prevents the students from
easily sharing their worksheet with someone else. They would have to
make a copy of the worksheet and then share that with someone first.
It sounds like keeping track of who a worksheet was ever shared with is
a good thing to add to the notebook.
Thanks,
Jason
I don't find any problem with cheating. Our lab is big enough to have
the students sit away from each other. My exams are with open books
and notes, so I am not concerned with them finding things on the
internet. We have software that allows the instructor to see what is
on each student's screen, but I never actually used it with this
group. I sit behind the students and walk around the room to make sure
they are not IMing. Since they know I can see any published worksheet,
they would not attempt it. To tell the truth, the students that
usually take this course are well known to me, so I basically trust
them.
Another idea a colleague gave me is to make part of the exam a "group
test". I am not ready to do that, but I will experiment this semester
with a "lab" in which I give them only one problem and they have to
give me the best solution they can come up with in 65 minutes.
The approach with lower-level classes with larger number of students
would have to be very different.
On Wed, Jan 19, 2011 at 12:54 AM, dimpase <dim...@gmail.com> wrote:
I had a similar problem with a recent Sage installation I made (In
ubuntu). I installed Sage, and SageTex according to the "official"
documentation (get SageTex from the Sage site, set a local texmf
structure, etc.), and had exceptions running sagetex.py
It so happened that texlive had an outdated version of sagetex.py. It
is sort of a chicken-and-egg thing. SageTex needs some packages
(makecmd.sty, or something like that), that are in the texlive-extras
package, which also comes with the bad sagetex.py. I guess they just
dump everything that is on CTAN in their package.
BTW, I am doing this because I wrote a program to help with automatic
generation of tests for our coordinated calculus. I'm not at a point
were I am ready to distribute it, and there is no documentation, but
if someone wants to try it, I'll be glad to send them a copy. It is
written in Python (what else?) and uses PyQT.
I would also be glad if someone could tell me what kind of licensing
info I have to distribute with the software. I never distributed
anything before...
This came up just a little while ago. SageTeX was part of TeXLive for
just long enough to "infect" lots of Linux packages, and there's nothing
we can do about it except wait for new TeXLive packages that don't
include SageTeX to come out. It'll take years. :(
Fortunately, I think you can put sagetex.sty in your personal texmf tree
and TeX will use that version. You can also demand a particular version
of sagetex.sty in your LaTeX file:
\usepackage{sagetex}[2010/10/20]
or similar.
In the meantime, there's now a mechanism in SageTeX to detect version
mismatches, but that doesn't help with the above problem...
Dan
--
--- Dan Drake
----- http://mathsci.kaist.ac.kr/~drake
-------
What I did is create a symbolic link from
~/Library/texmf/tex/generic/sagetex to
~/sage/local/share/texmf/tex/generic/sagetex. Then I always have ~/sage
point to my current version of sage. That way whenever I upgrade, the
sagetex.sty file in my personal texmf tree is automatically upgraded,
since it was just a symbolic link to my sage install.
I haven't had a problem with version mismatches since I did this, and I
don't even have to think about it anymore.
Jason
Did you regenerate your tex path list? Try doing
$ sudo texhash
Then do
$ kpsewhich sagetex.sty
and make sure that the path it prints out is your user tex path. For
example, I get:
$kpsewhich sagetex.sty
/Users/grout/Library/texmf/tex/generic/sagetex/sagetex.sty
Jason