search for: savely

rucker222 wrote: > The drop down layer selection menu at the top left of the screen directly above where the drawing 1 tab is opens upwards off of the screen once the drawing has a few layers on it. jjmckenzie wrote: > Log file please. I loaded a drawing with plenty of layers and then clicked on the layer drop down menu a couple of times before exiting ProgeCAD. Log file below. (sorry

On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote: > > - changes in the nouveau driver. Mika told me the PCIe regression > > "pcieport 0000:00:01.0: PME: Spurious native interrupt!" is supposed > > to be fixed in 5.8, but I still get a 4mn hang or so during boot and > > with 5.8, removing the USB key, didn't help make the boot faster >

Scenario: Here I am working away in R. I've got results that prove global warming is anthropogenic and also the solution for producing limitless carbon-neutral energy from nuclear fusion. Its been a good day. So, I want to save my work. I don't want to overwrite my current .RData, so I save it to another file: save(file="prize.RData") # just need to email this to the Nobel

When dealing with object holding pointers that are only valid during a single session, it would be convenient to exclude them from being saved with the session image. (I am assuming that `quit` calls `save.image` before quitting or is it internal?) Currently they are saved with the pointer converted to NULL. Its a bit surprising for users not realizing the object is no longer valid. My thought is

Greetings All, I am looking to write a parametrized Rscript that will accept a variable name(that also is the name of the flat file), transform the data into a data frame and preform various modeling on the structure and save the output and plot of the model. In this example i am using a rpart decision tree. The only problem i am having is integrating the parameter into the internal object name

On Mon, Sep 7, 2020 at 10:58 PM Marc MERLIN <marc_nouveau at merlins.org> wrote: > > On Mon, Sep 07, 2020 at 09:14:03PM +0200, Karol Herbst wrote: > > > - changes in the nouveau driver. Mika told me the PCIe regression > > > "pcieport 0000:00:01.0: PME: Spurious native interrupt!" is supposed > > > to be fixed in 5.8, but I still get a 4mn hang

Hello, I have the following structure: model foo has_many :bars:, :dependent => true end model bar belongs_to :foo end In my action, when i try to save foo: def save begin f = foo.new f.a = 5 begin b = bar.new b.a = 10 f.bars << b rescue Exception => exc ... end f.save! <-- This does not happen

Dear R-users, I am trying to write a wrapper function around save() that will report the file which is being saved to. So I thought that the followintg would do the trick, but it doesn't. I understand that 'y' is somehow not visible inside save.verbose, but don't know how to fix this. save.verbose <- function(..., file) { cat("save.verbose:", file, "\n")

> rucker222 wrote: > The convert PDF to DXF function does not work (found in the file menu). Below is the output at the Command line when I try to use it. > > Command : _PDF2CAD > 1Vbi file not found > > there does not appear to be an error to copy from the terminal. jjmckenzie wrote: > Interesting. This looks like a 'file not found error' but the first part

Hi, I'm new to Linux and even newer to wine. I'm using the latest release of wine 1.3.20 on U10.10 - the Maverick Meerkat. I work as an AutoCAD Draft Person and as much as I have fallen in love with my Ubuntu OS I am really disappointed with the lack of quality CAD software. I came across ProgeCAD (2010 Pro) on a couple of forums and saw in the AppDB section that ProgeCAD has some

Hi, If anyone has some time to help with my problem that would be really good :) I am getting a "stack level too deep" error when saving an object to the database when it is has a has_one relationship to another object I wish to save and associate after it. If goes a little like this class Quote < ActiveRecord::Base belongs_to :eventdetail has_many :bookings # An

I have changed the default in save() to compress = !ascii. This seems quite safe, as almost always save() is called explicitly and people will appreciate that it might take a little time to save large objects (and depending on your system, compression could even be faster). Should we also change the default in save.image()? That is almost always used implicitly, via q(), a menu .... There

Hi, I've been slowly transitioning to saving sets of objects for a project using save() rather than cluttering my workspace and then doing save.image() However, sometimes after I have done say: save(x,y,z, file='work.Rda') and I reload it a little later and I see that I also want to save object p. Currently I need to do: save(x,y,z,p, file='work.Rda') Is there any way

Ok, I have an update to this problem. I added the nouveau list because I can't quite tell if the issue is: - the PCIe changes that went in 5.6 I think (or 5.5?), referenced below - a new issue with thunderbold on thinkpad P73, that seems to be triggered if I have a USB-C yubikey in the port. With 5.7, my issues went away if I removed the USB key during boot, showing an interaction

Hi all! I don't religiously follow everything that pops up in the selinux alerts, but now and then I go back and look at some of them. (I'm on an up to date Centos-7). Today I noted an error that seems to occur during a weekly raid check, from /etc/cron.d. the selinux alert is: SELinux is preventing /usr/sbin/mdadm from write access on the file /var/log/rear/rear-fcshome.log.lockless.

https://bugzilla.netfilter.org/show_bug.cgi?id=1750 Bug ID: 1750 Summary: 'ipset save' does not save in format loadable by systemd (it saves in 'ipset list' format) Product: ipset Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: normal

Hi, Today I came upon unexpected R behaviour. I did some modelling and the result was R object, about 28MB size (nested list, with matrixes as list elements). When I was saving the session with save.image, the resulting .RData file was 300MB. There were no other large objects: >

Hello, I created an array to hold the results of a series of simulations I'm running: d.eta <- array(0,dim=c(3,3,200)) <simulation goes here and populates the array but it's not important> Then I tried to save the results using this: save(d.eta,file="D:/Simulation Results/sim 9-23-11 deta") When I later tried to reload them using this: d.eta <-

Is there a way to save EVERYTHING in R? Hi all, Could you please shed some lights on me about this? I am trying to see if there is a way to save EVERYTHING in R to a file, something like "save.image"... But "save.image" doesn't save environment variables such as those properties that are obtained using "Sys.getenv()" function... So is there a way to save

On Tue, Sep 08, 2020 at 01:51:19AM +0200, Karol Herbst wrote: > oh, I somehow missed that "disp ctor failed" message. I think that > might explain why things are a bit hanging. From the top of my head I > am not sure if that's something known or something new. But just in > case I CCed Lyude and Ben. And I think booting with > nouveau.debug=disp=trace could already