Skip to content
Snippets Groups Projects
Select Git revision
  • c18b97d9b1fb528c17347126a4bcf2bbbe13166f
  • master default protected
  • dev protected
  • Issue/3003-stsInstitute
  • gitkeep
  • Issue/2449-GuidPidSlugToProjectSettings
  • Issue/2309-docs
  • Fix/xxxx-updateDependencies
  • Issue/2364-testingKpiParser
  • Issue/2287-guestRole
  • Test/xxxx-pipelineTriggers
  • Issue/2102-gitLabResTypeRCV
  • Issue/2278-gitlabToS
  • Issue/2101-gitLabResTypeUi
  • Issue/1788-extractionCronjob
  • Issue/2183-kpiGeneratorResource
  • Issue/2222-resourceDateCreated
  • Issue/2221-projectDateCreated
  • Issue/1321-pidEnquiryOverhaul
  • Issue/1999-gitlabResourcesLib
  • Issue/1951-quotaImplementation
  • v2.22.0
  • v2.20.0
  • v2.19.1
  • v2.19.0
  • v2.18.0
  • v2.17.0
  • v2.16.2
  • v2.16.1
  • v2.16.0
  • v2.15.0
  • v2.14.0
  • v2.13.0
  • v2.12.1
  • v2.12.0
  • v2.11.1
  • v2.11.0
  • v2.10.1
  • v2.10.0
  • v2.9.1
  • v2.9.0
41 results

Database.Tests.csproj

Blame
  • Code owners
    Assign users and groups as approvers for specific file changes. Learn more.
    PlotID_config.m 1.07 KiB
    %% Working with one config file
    
    %% add custom publish options to the config file
    % you can define custom options in the config file:
    
    configFileName = 'config.json';
    configObj = PlotID.config(configFileName);
    
    % This method adds the default config to your config file
    configObj.addPublishOptions('default');
    % You can change this in the json file, but be carefull no
    % argumentValidation will be done on options from the config file!
    
    %% Working with multiple (project dependend) config files
    % it is possible to use individual config files for each project
    % configP1.json, configP2.json ... 
    
    % Create a new config file programatically 
    customConfigFileName = 'configP1.json';
    configObj = PlotID.config(customConfigFileName);
    configObj.addPublishOptions('default');
    
    % Use the custom Config
    % you need to provide the name of your custom config file to tagplot as
    % well as to publish by using the Name-Value Pair:
    % 'ConfigFileName','YOURNAME.json'
    
    % [figs, IDs] = PlotID.TagPlot(figs, 'ConfigFileName','configP1.json');
    % Publish(DataPaths,scriptPath, 'ConfigFileName','configP1.json')