13
$\begingroup$

I am running Ma 10.3. When I try to Get SciDraw package I get the following error:

AppendTo[$Path, "C:\\Users\\username\\mathematica"];
Get["SciDraw`"]

SetDelayed::write: "Tag MissingQ in MissingQ[expr_] is Protected".

Can someone confirm the problem?

Update

The Mathematicas v10-v10.3 contain bugs regardinng using a custom function for ticks and maybe this problem is inter-related. In v10.4, one can use a custom function again but for log scales, wolfram changed syntax so that it sends min and max values scaled rather than as in v9, however, in some cases, mathematica still sends unscaled values (FrameTicks or a composed function). See this post.

$\endgroup$
5
  • $\begingroup$ Yes, unfortunately I can confirm that; it may be even a bit worse on my system: image. I am using 10.4 on Win7-64. $\endgroup$
    – MarcoB
    Mar 18, 2016 at 18:34
  • $\begingroup$ Nevertheless, the basic functionality of the package seem to be retained. Quick test: image. $\endgroup$
    – MarcoB
    Mar 18, 2016 at 18:52
  • 1
    $\begingroup$ I also had multiple errors when loading the package which were caused by an old CustomTicks or LevelScheme .m package file that was stil sitting in one of the Applications folders. $\endgroup$ Mar 19, 2016 at 9:57
  • $\begingroup$ v10-10.3 contain a bug regarding ticks where it is not possible to use custom function for generating ticks, v10.4 does not have this bug but the logic of ticks has been changed quite a lot and CustomTicks will not work for LogPlot. See this post $\endgroup$
    – leosenko
    Apr 11, 2016 at 18:54
  • $\begingroup$ I also see this in Linux (10.3.1) $\endgroup$ Apr 11, 2016 at 19:30

2 Answers 2

12
$\begingroup$

Unfortunately, SciDraw does indeed cause error messages because SciDraw tries to define functions which have been introduced into the core Wolfram language since SciDraw was introduced. One of these probably started in v10.2, over MissingQ, and the other probably dates to v10.4, over BoundingRegion. Users with earlier versions of Mathematica are unlikely to encounter these issues.

MissingQ, v10.2 and later

This is the error you found. Some digging around locates the following definition in FigData.m,

MissingQ[expr_] := ! FreeQ[expr, Missing];

with some text notes on the corresponding section of FigData.nb that indicate that this section is still relatively rough around the edges. This defines a pretty reasonable function, to check whether expr is 'missing', in the formal sense that it includes objects of the form Missing["reason"].

Unfortunately, a very similar function of the same name, MissingQ, was introduced in v10.2, with a slightly narrower meaning:

MissingQ[expr] gives True if expr has head Missing.

That is, MissingQ[2 Missing[]] will return True in the SciDraw implementation and False in the core implementation.

However, as far as I can tell, SciDraw's MissingQ is not used anywhere else in the code - indeed, it is not assigned a usage message, which is a good flag that it's not meant to be used yet - so if the message bothers you, it's probably safe to simply comment that line out. You're unlikely to break anything that isn't already broken (the error message indicates that the intended (re)definition of the function failed anyway.

BoundingRegion, v10.4 and later

As pointed out in the comments, there's a second error message - actually a pair of them - in later versions of Mathematica:

SetDelayed::write: Tag BoundingRegion in BoundingRegion[ObjectList:{(_Object?(And[
  <<2>>]&)|_?(And[<<2>>]&)|_Object?(And[<<2>>]&)|_?(And[<<2>>]&))..}] is Protected.

SetDelayed::write: Tag BoundingRegion in BoundingRegion[obj:_Object?(ObjectExistsQ[
  Slot[<<1>>]]&&MemberQ[ClassAncestry[<<1>>],FigAnchor]&)|_?(ObjectExistsQ[Object[
  <<1>>]]&&MemberQ[ClassAncestry[<<1>>],FigAnchor]&)|_Object?(ObjectExistsQ[Slot[
  <<1>>]]&&MemberQ[ClassAncestry[<<1>>],FigObject]&)|_?(ObjectExistsQ[Object[
  <<1>>]]&&MemberQ[ClassAncestry[<<1>>],FigObject]&)] is Protected.

The problem is exactly the same one, caused by the following definition in SciDraw's FigGeometry.m,

BoundingRegion[
  ObjectList:{(ObjectPattern[FigAnchor] | ObjectNamePattern[FigAnchor] | 
               ObjectPattern[FigObject] | ObjectNamePattern[FigObject] )..}
]:=Module[
    {},
    FigCheckInFigure[BoundingRegion];
    Canvas[ObjectCanvasBox[ObjectList]]
];

BoundingRegion[
  obj:((ObjectPattern[FigAnchor] | ObjectNamePattern[FigAnchor] | 
        ObjectPattern[FigObject] | ObjectNamePattern[FigObject] ))
]:=BoundingRegion[{obj}];

DeclareFigFallThroughError[BoundingRegion];

with the usage message

BoundingRegion[{p1,p2,…,obj1,obj2,…}] returns a region specification Canvas[{{xmin,xmax},{ymin,ymax}}] for the bounding box surrounding the given objects or points/anchors.

It is also documented in §7.4 of the SciDraw user guide, as

BoundingRegion[{p1,p2,…,obj1, obj2,…}]Returns a region specification which circumscribes the given points (or anchors) p1, p2, …, and objects obj1, obj2, …

The corresponding function, BoundingRegion, was introduced into the core language in v10.4, and it does do roughly the same sort of thing, but unfortunately the details are rather different:

BoundingRegion[{pt1, pt2,…}] gives the minimal axis-aligned bounding box for the points pt1, pt2, ….

BoundingRegion[{pt1, pt2,…},form] gives a bounding region of type form.

BoundingRegion[mesh,…] gives a bounding region for a MeshRegion or BoundaryMeshRegion.

This means that the two functions cannot really be substituted for each other. Fortunately, the situation is only slightly worse than with MissingQ:

  • BoundingRegion is not used elsewhere in the package as far as I can tell, so the conflict doesn't break anything else (and neither would removing the definition). It is defined as a user-accessible function, which is now lost. This will need to be addressed in future versions of the package.
  • Similarly to MissingQ, the error message indicates that the proposed (re)definition did not succeed, so if the error message bothers you, you can comment out those lines and the package's function will be identical.

This answer is current as of v11.0.0. Because of the nature of the functions defined in SciDraw, it's possible that further clashes will develop in the future - but hopefully not!

$\endgroup$
5
$\begingroup$

The following should allow you to make SciDraw work in Mathematica version 13.0. It works by parsing all of the package files and replacing symbol names that conflict with System symbols. So all occurrences of Canvas in the package code are replaced with SDCanvas, for example.

This doesn't do anything to change the notebook files the packages are derived from, mainly because I don't know how to programmatically replace symbols in notebooks.

To start download and unzip the package to your hard drive and locate the package files

$packagesDir = "..../SciDraw-0.0.7/packages";

files = File /@ FileNames["*.m", $packagesDir, Infinity];

I've dabbled recently with automated code refactoring using the code parser so that's what I'm doing here. It may be overkill for this compared to normal string pattern replacement, but it allows me only to replace occurrences of symbols and exclude all strings and other data types.

=

Get @ "CodeParser`";
SetOptions[CodeParser`CodeParse, SourceConvention -> "SourceCharacterIndex"];
symbolsToReplace = <|
    "BoundingRegion" -> "SDBoundingRegion", "Canvas" -> "SDCanvas", "ObjectExistsQ" -> "SDObjectExistsQ",
    "MissingQ" -> "SDMissingQ"
|>;
getReplacements[ast_][symbol_, replacement_] := Apply[
    Sequence,
    DeleteDuplicates[
        Cases[ast,
            CodeParser`LeafNode[Symbol, symbol, <|Rule[Source, s_]|>] :> {replacement, s},
            Infinity
        ]
    ]
];
fixFile[file_File] := Module[
    {ast, replacements, string = Import[file, "String"]},
    ast = CodeParser`CodeParse @ file;
    replacements = KeyValueMap[getReplacements @ ast, symbolsToReplace];
    If[Not[MatchQ[replacements, {Repeated[{_, _}]}]],
        Return[Null, Module]
    ];
    replacements = Transpose @ replacements;
    Export[file,
        StringReplacePart[string, replacements[[1]], replacements[[2]]],
        "String"
    ]
]

Now run the fix over the list of files

Scan[fixFile, files]

After this the packages should load well aside from a shadowing message about the option name AxisLabels. This is a nonissue really since options can generally be given with context or even as a string.

$packagesDir = "/Users/jasonb/Downloads/SciDraw-0.0.7/packages";

AppendTo[$Path, $packagesDir];
<<SciDraw`

The package loads fine, but it didn't modify the documentation notebooks. Running those examples, or any old code you have for SciDraw, will give errors because that code still uses Canvas instead of SDCanvas, for example. To run those examples, you can use a simple wrapper like this

Attributes[sciDraw] = {HoldAll};
sciDraw[args__] := Block[
  {BoundingRegion = SDBoundingRegion, Canvas = SDCanvas},
  args
]

Using the above function I was able to run most examples in the notebook "Examples-Diagrams.nb", making for example this figure

enter image description here

I hope this helps.

$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.