What moved, what's gone, and what's renamed#
1. Repository reorganization#
RAVEN 2's top-level layout (core/, external/, hpa/, io/, legacy/,
pathway/, plotting/, solver/, struct_conversion/, installation/,
utils/) has been replaced with functional folders that group functions by what
they do rather than by legacy history:
RAVEN 3 folder |
Contents |
Mostly came from (RAVEN 2) |
|---|---|---|
|
|
|
|
FBA-adjacent analyses: FVA, sampling, FSEOF, OptKnock, robustness, production envelope, flux comparison/tracing |
|
|
MIRIAM editing, SBO term assignment, ΔG CSV I/O |
|
|
Biomass composition fitting/scaling, GAM |
|
|
Multi-model comparison, structured model diffing |
|
|
Applying a data-driven growth/media condition to a model |
new folder |
|
RAVEN⇄COBRA conversion, identifier prefixing, field ordering |
|
|
Genome-annotation-driven gene/model curation |
new folder |
|
|
|
|
Path setup, on-demand binary/data download |
|
|
Model import/export (SBML, YAML, Excel), FASTA I/O |
|
|
Subcellular localization prediction/scoring, compartment assignment |
|
|
Structural edits: add/remove/change rxns, mets, genes; merge, sort, simplify |
|
|
Non-mutating lookups: indexes, exchange/transport reactions, stoichiometry construction, model checking |
|
|
KEGG- and homology-based draft reconstruction |
|
|
LP/MILP solving |
|
|
Metabolic task list parsing/checking |
|
|
|
|
|
Generic helpers, including the new argument-parsing/registry infrastructure |
|
|
Thin backward-compatible wrappers for merged/renamed functions |
new folder |
Entirely removed (no successor folder): external/metacyc/ (MetaCyc
reconstruction), pathway/ and plotting/ (visualization), legacy/
(CellDesigner import and other pre-2.0 code), struct_conversion/'s Excel-POI
helpers.
The reorganization affects fewer scripts than the change list suggests.
If your scripts call RAVEN
functions by name (the normal usage pattern, with the whole RAVEN folder tree,
including subfolders, added to the MATLAB path via addRavenToUserPath or
addpath(genpath(...))), moving a file to a new subfolder does not break the
call: MATLAB resolves functions by name across the whole path, not by a
hard-coded relative location. The reorganization only matters if you (a)
hard-coded a path to a specific .m file, (b) called one of the functions that
was actually removed or merged (see below), or (c) shadowed a RAVEN function
name with your own; folder names are irrelevant otherwise.
The full moved-file mapping (RAVEN 2 path → RAVEN 3 path) is not reproduced here because it is large and, as the point above explains, rarely something you need to act on.
2. Removed functionality#
Beyond the items already listed as backward-incompatible above, RAVEN 3 removed a number of functions and whole subsystems as part of a deliberate effort to make the codebase smaller. None of these have call sites left in RAVEN 3 itself.
Removed |
What it did |
Replacement / notes |
|---|---|---|
|
Metabolic map/pathway visualization |
None in RAVEN core. Use COBRA Toolbox, Escher, or export flux/omics data for external plotting. |
|
MetaCyc-based draft reconstruction |
None; KEGG- and homology-based reconstruction remain the supported paths. |
|
Pre-2.0 compatibility code |
None; considered dead. |
|
Apache-POI-based Excel model I/O |
|
|
SIF graph export; tab-delimited model export |
Dead/orphaned code with no callers; removed outright. |
|
Path canonicalization; file MD5 hashing; toolbox git-version lookup |
Inlined where still needed (e.g. MD5 via Java's |
|
Universal error/warning display |
Native |
|
Flux-change reporting relative to a reference solution |
|
|
Printed reactions to screen/file |
|
|
Returned metabolite indices in a given compartment |
Inline it as |
|
Remapped compartment labels in a localization-score structure |
Superseded by the new predictor-based localization workflow and |
|
Loaded an expression-experiment structure from an ad hoc Excel format |
Superseded by |
|
Per-reaction reactant/product synthesizability debugging |
No direct successor; use |
|
Parallel Computing Toolbox pool setup |
Renamed/rewritten as |
|
WoLF PSORT score parsing |
None; see §3. |
|
Local-KEGG-FTP-dump parsing; per-KO multi-FASTA assembly; WSL path translation; Excel-based BLAST import |
Superseded by the raven-data-artifact-based KEGG pipeline. See §7. |
|
MOMA-based analyses (quadratic programming) |
Removed; no in-toolbox QP-based replacement. See §3 for |
|
Ad hoc test scripts |
|
3. Renamed, merged, and consolidated functions#
RAVEN 3 introduces a formal deprecated/ folder convention: functions that
were merged into a more general replacement stay callable under their old name,
as a thin wrapper that emits a one-time RAVEN:deprecated warning ("will be
removed in the next major release") and forwards to the new function.
Old function(s) |
New function |
Notes |
|---|---|---|
|
|
Argument order maps 1:1; the wrapper forwards |
|
|
Not a verbatim forward: |
|
|
|
|
|
|
|
folded into |
Its rxn/gene/met/comp overlap output is now one part of |
|
|
Merged, not renamed. RAVEN 2 had both |
|
folded into |
Exposed now via |
|
folded into |
|
|
|
Not a direct signature-compatible rename: the whole data source changed; see §7. |
|
|
Moved from |
Separately, getINITModel and runINIT (now under INIT/tINIT/) are marked
legacy but indefinitely supported (not on the deprecated/ removal track)
via utils/legacyMethodNotice.m, which fires a one-time, silenceable
RAVEN:legacyMethod warning pointing at ftINIT. Use ftINIT for new work;
keep getINITModel/runINIT only to reproduce models originally built with
them.