Just pointing out that if you do not want to SEE an error message that is
otherwise harmless, one option in R is to let the error happen but arrange
to deal with it in some way including just suppressing the message.
On Tue, Oct 3, 2023, 5:27 AM Duncan Murdoch
wrote:
> On 02/10/2023 10:17 p.m.,
On Tue, 3 Oct 2023 16:50:55 +
"Koenker, Roger W" wrote:
> I thought it might come from Rmosek, but mosek folks don’t think so.
I downloaded the Rmosek source package using
download.packages(
'Rmosek', '.',
repos='https://download.mosek.com/R/10.1'
)
...and there are the deprecated calls
There is a call to mosek and I assumed that this wasn’t going to be helpful for
most R-devel recipients. I tried Duncan’s very reasonable suggestion about
options() but it didn’t produce the desired error, so perhaps this isn’t really
a warning but something else???
For those who might have r
> Duncan Murdoch
> on Tue, 3 Oct 2023 12:59:10 -0400 writes:
> On 03/10/2023 12:50 p.m., Koenker, Roger W wrote:
>> I’ve been getting this warning for a while now (about
>> five years if memory serves) and I’m finally tired of it,
>> but also too tired to track it down
On 03/10/2023 12:50 p.m., Koenker, Roger W wrote:
I’ve been getting this warning for a while now (about five years if memory
serves) and I’m finally tired of it, but also too tired to track it down in
Matrix. As far as I can grep I have no reference to either deprecated object,
only the appa
I’ve been getting this warning for a while now (about five years if memory
serves) and I’m finally tired of it, but also too tired to track it down in
Matrix. As far as I can grep I have no reference to either deprecated object,
only the apparently innocuous Matrix::Matrix(A, sparse = TRUE).
Dear Luke Tierney,
Thank you for the reply and apologies for not getting back to you
earlier.
On Fri, 22 Sep 2023 16:14:58 -0500 (CDT)
luke-tier...@uiowa.edu wrote:
> I think it would be best to modify errorcall so errorcall_cpy is not
> necessary. As things are now it is just too easy to forget
On 02/10/2023 10:17 p.m., Trevor Davis wrote:
> Thanks! However, isn't length(dev.list()) == 0 when there are no
devices? That's what I'm seeing on MacOS.
Ifthere is only one graphics device then R should automatically set it
as the active graphics device so it isn't really necessary to manu
Simon,
Many thanks for your advice! The issue was that another package was
inheriting from the "mirt" class in question. Apparently, some methods are
cached at build time (is this documented anywhere?). After reinstalling the
package that extends the "mirt" class, the proper method is now being
di
